Looking at the 5/1 nightly build Parameter serializer code, I see the
QName soapType = SoapEncUtils.getAttributeValue(paramEl,
as the code that pulls the value of xsi:type
However, I notice that the Constants.NS_URI_CURRENT_SCHEMA_XSI is set tp
So for the raleigh exercise, did you get things interoperating with MSTK by
recompiling to set NS_URI_CURRENT_SCHEMA_XSI to NS_URI_2001_SCHEMA_XSI
instead? Or did you take another approach?
I'm trying to get an apache client working against a 2001 server myself.
Dropping in the latest nightly didn't work in terms of having it recognize
2001, right out of the box...
> -----Original Message-----
> From: Sam Ruby [mailto:rubys@...]
> Sent: Saturday, April 28, 2001 6:22 PM
> To: email@example.com
> Subject: RE: [soapbuilders] Re: question regarding moving to 2001
> Tony Hong wrote:
> > My experience has been that Apache SOAP cannot handle messages that use
> > 2001 schema - only 1999 is recognized. Thus, I would expect that as of
> > today, there is complete non-interoperability between Apache and an MS
> > endpoint that is returning 2001, which is the default.
> > Doug, how were you able to tweak it so that you got this to work? Or ,
> > the MS endpoint configured to return 1999 rather than 2001?
> The latest builds support 1999, 2000/10, and 2001. That's also why it was
> not a problem getting these two to talk during the interop event in
> If you want to take a peek for yourself:
> - Sam Ruby
> To unsubscribe from this group, send an email to:
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/