Can you post more specifics about the problems you are experiencing? There are some well-known interop issues between Microsoft implementations and Apache SOAP. Some of these have workarounds. If you are using .NET and want to maximize interoperability with Apache SOAP (as well as other SOAP implementations), you should specify SoapRpc services and/or methods, rather than accepting the defaults. Microsoft defaults to the document/literal encoding defined in the WSDL specification. Apache SOAP (and, again, several other SOAP implementations) does not support document/literal encoding as fully as rpc/encoded (which is basically what the SOAP spec defines).
If you *must* use doc/lit, I highly recommend you consider using Apache Axis (http://xml.apache.org/axis). It supports WSDL and doc/lit. It is at the point of issuing release candidates, with a "production" release coming very soon. Scott Nichol ----- Original Message ----- From: "Damian Alonso" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 01, 2002 11:15 PM Subject: RE: Extra line appearing in Apache Response > On this issue, (I was the one who originally posted the problem) I have > found that the problem relates to the XML Schema that .NET uses to validate > its XML. Again, another interop problem which when we looked at the SOAP > Specification, it didn't really say much about it. The specific problem we > have found is using namespaces in the tags (Apache seems to use 'ns1' in the > tags, which breaks the XML Schema of .NET). > > Anyone heard about this issue before?? > > btw - thanks to everybody for the feedback on the original issue. > > Damian. > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 02, 2002 1:08 PM > To: [EMAIL PROTECTED] > Subject: RE: Extra line appearing in Apache Response > > > Then it should be fixed, IMHO. This is causing interop problem. > > XML spec talks about significant and insignificant white space. > I am not clear on this. What does SOAP spec mandate -- looked > like SUN's SOAP server implementation goes by a strict XML schema. > > Soumen Sarkar. > > -----Original Message----- > From: Scott Nichol [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 01, 2002 8:07 PM > To: [EMAIL PROTECTED] > Subject: Re: Extra line appearing in Apache Response > > > > In order to fix the problem for myself, I had to download Apache SOAP > > sources and edit class org.apache.soap.util.StringUtils, replacing > > > > public static final String lineSeparator = > > System.getProperty("line.separator", "\n"); > > > > with an easy > > > > public static final String lineSeparator = ""; > > > > Then I had to recomplie SOAP lib, and use custom buit jar. This solved > my > > problem completely. Now I wonder, what is the specific reason to > insert new > > lines? > > It is just for readability, which means it is only useful when you have > to debug. > > Scott Nichol > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
