axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew J. Duftler" <duft...@watson.ibm.com>
Subject RE: cvs commit: xml-axis/java/src/org/apache/axis/utils/cache JavaMethod.java
Date Wed, 06 Jun 2001 04:01:08 GMT
> We obviously are going to need some sort of Service Description to handle
> that case.  One format to be supported will be xml-soap V2's.  A format
> that I see as potentially far more popular will be the Web Service
> Description Language, i.e., WSDL.

As you say, that's the obvious future direction.

My question was, "What does Axis do now on the client-side when xsi:type
attributes are not present?"

Thanks,
-Matt

> -----Original Message-----
> From: Sam Ruby [mailto:rubys@us.ibm.com]
> Sent: Tuesday, June 05, 2001 8:39 PM
> To: axis-dev@xml.apache.org
> Subject: RE: cvs commit: xml-axis/java/src/org/apache/axis/utils/cache
> JavaMethod.java
>
>
> Matthew J. Duftler wrote:
> >
> > How does this work on the client-side? I can see the server-side
> exploiting
> > reflection to obtain type information, but what do you do now on the
> > client-side when things come back without xsi:type attributes? Is this
> part
> > of the client-side deployment info?
>
> We obviously are going to need some sort of Service Description to handle
> that case.  One format to be supported will be xml-soap V2's.  A format
> that I see as potentially far more popular will be the Web Service
> Description Language, i.e., WSDL.
>
> - Sam Ruby
>


Mime
View raw message