Re: Axis 1.4 server -> .NET 2.0 client - Doc/Literal namespace? trouble
On 10/18/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: I'm thinking that there must be something wrong with the way you generated or deployed your service, because otherwise no one would be able to get Axis 1.4 to work using the code-first approach, and I know that people are doing so. WSDL-first will certainly solve your problem. You can also do the java2wsdl / wsdl2java approach. Oh. Wasn't aware of java2wsdl tooling. Will try that and investigate my deployment descriptors. Thanks for your help! Anne On 10/18/06, Philipp Stader <[EMAIL PROTECTED]> wrote: > Thanks for reply once again! Is this something i can do about (beyond > going for the wsdl first approach)? Or worth a jira report? > > Phil > > On 10/17/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > > There's a namespace error in the response message. According to the > > WSDL, the response message should look like this (or the semantic > > equivalent): > > > > > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > > >http://webservice.psr.datamigration.ch";> > > http://www.data-migration.ch/";> > >Dan Diephouse > >0123456789 > >2006-10-16T14:10:39.796Z > >Mon Oct 16 16:10:39 CEST > > 2006 > >Using XFire > > > > > > > > > > > > Anne > > > > On 10/16/06, Philipp Stader <[EMAIL PROTECTED]> wrote: > > > Thank you very much for your reply! > > > > > > On 10/15/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > > > > How did you generate the WSDL? > > > > (The WSDL and the response message don't match.) > > > > > > > > For best result, generate a wrapped style service. > > > > > > I am using wrapped/literal now. The Wsdl is generated through Axis > > > "on-the-fly". Maybe i mixed something up compiling the mail. Here is > > > what i am testing with right now. When calling getBookByISBN the Book > > > Object gets instantiated by .NET but all properties are null. Same > > > Java class files using XFire as Soap Stack work for me. I will try > > > Axis 2 1.1 too but we have quite some installations using Axis 1.4 and > > > would like to keep it for now. > > > > > > deploy.wsdd, wsdl generated by Axis and Soap Request / Response to follow. > > > > > > Axis 1.4 is deployed on a Tomcat 4.1.31 using Java SDK 1.4.2_12 > > > > > > deploy.wsdd for Axis > > > > > > http://xml.apache.org/axis/wsdd/"; > > > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"; > > > xmlns:dmns="http://www.data-migration.ch/";> > > > > > style="wrapped" use="literal"> > > > > > value="ch.datamigration.psr.webservice.BookController"/> > > > > > > > > type="java:ch.datamigration.psr.webservice.Book"/> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > The wsdl Axis generates looks like this: > > > > > > > > > > > targetNamespace="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; > > > xmlns:apachesoap="http://xml.apache.org/xml-soap"; > > > xmlns:impl="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; > > > xmlns:intf="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; > > > xmlns:tns1="http://webservice.psr.datamigration.ch"; > > > xmlns:tns2="http://www.data-migration.ch/"; > > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > > > xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > > > > > > > > >> > targetNamespace="http://webservice.psr.datamigration.ch"; > > > xmlns="http://www.w3.org/2001/XMLSchema";> > > >http://www.data-migration.ch/"/> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> > targetNamespace="http://www.data-migration.ch/"; > > > xmlns="http://www.w3.org/2001/XMLSchema";> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > name="getBookByISBNRequest"/> > > > > > name="getBookByISBNResponse"/> > > > > > > > > > > > type="impl:BookController"> > > >> > transport="http://schemas.xmlsoap.org/soap/http"/> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> > name="AxisBookWrappedLiteral"> > > > > > location="http://192.168.155.254:8080/axis/services/AxisBookWrappedLiteral"/> > > > > > > > > > > > > > > > The Soap Request: > > > > > > > > > > > targetNamespace="ht
Re: Axis 1.4 server -> .NET 2.0 client - Doc/Literal namespace? trouble
I'm thinking that there must be something wrong with the way you generated or deployed your service, because otherwise no one would be able to get Axis 1.4 to work using the code-first approach, and I know that people are doing so. WSDL-first will certainly solve your problem. You can also do the java2wsdl / wsdl2java approach. Anne On 10/18/06, Philipp Stader <[EMAIL PROTECTED]> wrote: Thanks for reply once again! Is this something i can do about (beyond going for the wsdl first approach)? Or worth a jira report? Phil On 10/17/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > There's a namespace error in the response message. According to the > WSDL, the response message should look like this (or the semantic > equivalent): > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > >http://webservice.psr.datamigration.ch";> > http://www.data-migration.ch/";> >Dan Diephouse >0123456789 >2006-10-16T14:10:39.796Z >Mon Oct 16 16:10:39 CEST > 2006 >Using XFire > > > > > > Anne > > On 10/16/06, Philipp Stader <[EMAIL PROTECTED]> wrote: > > Thank you very much for your reply! > > > > On 10/15/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > > > How did you generate the WSDL? > > > (The WSDL and the response message don't match.) > > > > > > For best result, generate a wrapped style service. > > > > I am using wrapped/literal now. The Wsdl is generated through Axis > > "on-the-fly". Maybe i mixed something up compiling the mail. Here is > > what i am testing with right now. When calling getBookByISBN the Book > > Object gets instantiated by .NET but all properties are null. Same > > Java class files using XFire as Soap Stack work for me. I will try > > Axis 2 1.1 too but we have quite some installations using Axis 1.4 and > > would like to keep it for now. > > > > deploy.wsdd, wsdl generated by Axis and Soap Request / Response to follow. > > > > Axis 1.4 is deployed on a Tomcat 4.1.31 using Java SDK 1.4.2_12 > > > > deploy.wsdd for Axis > > > > http://xml.apache.org/axis/wsdd/"; > > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"; > > xmlns:dmns="http://www.data-migration.ch/";> > > > style="wrapped" use="literal"> > > > value="ch.datamigration.psr.webservice.BookController"/> > > > > > type="java:ch.datamigration.psr.webservice.Book"/> > > > > > > > > > > > > > > > > > > > > The wsdl Axis generates looks like this: > > > > > > > targetNamespace="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; > > xmlns:apachesoap="http://xml.apache.org/xml-soap"; > > xmlns:impl="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; > > xmlns:intf="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; > > xmlns:tns1="http://webservice.psr.datamigration.ch"; > > xmlns:tns2="http://www.data-migration.ch/"; > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > > xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; > > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > > > > > >> targetNamespace="http://webservice.psr.datamigration.ch"; > > xmlns="http://www.w3.org/2001/XMLSchema";> > >http://www.data-migration.ch/"/> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> targetNamespace="http://www.data-migration.ch/"; > > xmlns="http://www.w3.org/2001/XMLSchema";> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > name="getBookByISBNRequest"/> > > > name="getBookByISBNResponse"/> > > > > > > > type="impl:BookController"> > >> transport="http://schemas.xmlsoap.org/soap/http"/> > > > > > > > > > > > > > > > > > > > > > > > >> name="AxisBookWrappedLiteral"> > > > location="http://192.168.155.254:8080/axis/services/AxisBookWrappedLiteral"/> > > > > > > > > > > The Soap Request: > > > > > > > targetNamespace="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; > > xmlns:apachesoap="http://xml.apache.org/xml-soap"; > > xmlns:impl="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; > > xmlns:intf="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; > > xmlns:tns1="http://webservice.psr.datamigration.ch"; > > xmlns:tns2="http://www.data-migration.ch/"; > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > > xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; > > xmlns:xsd="http:/
Re: Axis 1.4 server -> .NET 2.0 client - Doc/Literal namespace? trouble
Thanks for reply once again! Is this something i can do about (beyond going for the wsdl first approach)? Or worth a jira report? Phil On 10/17/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: There's a namespace error in the response message. According to the WSDL, the response message should look like this (or the semantic equivalent): http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> http://webservice.psr.datamigration.ch";> http://www.data-migration.ch/";> Dan Diephouse 0123456789 2006-10-16T14:10:39.796Z Mon Oct 16 16:10:39 CEST 2006 Using XFire Anne On 10/16/06, Philipp Stader <[EMAIL PROTECTED]> wrote: > Thank you very much for your reply! > > On 10/15/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > > How did you generate the WSDL? > > (The WSDL and the response message don't match.) > > > > For best result, generate a wrapped style service. > > I am using wrapped/literal now. The Wsdl is generated through Axis > "on-the-fly". Maybe i mixed something up compiling the mail. Here is > what i am testing with right now. When calling getBookByISBN the Book > Object gets instantiated by .NET but all properties are null. Same > Java class files using XFire as Soap Stack work for me. I will try > Axis 2 1.1 too but we have quite some installations using Axis 1.4 and > would like to keep it for now. > > deploy.wsdd, wsdl generated by Axis and Soap Request / Response to follow. > > Axis 1.4 is deployed on a Tomcat 4.1.31 using Java SDK 1.4.2_12 > > deploy.wsdd for Axis > > http://xml.apache.org/axis/wsdd/"; > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"; > xmlns:dmns="http://www.data-migration.ch/";> > style="wrapped" use="literal"> > value="ch.datamigration.psr.webservice.BookController"/> > > type="java:ch.datamigration.psr.webservice.Book"/> > > > > > > > > > > The wsdl Axis generates looks like this: > > > targetNamespace="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; > xmlns:apachesoap="http://xml.apache.org/xml-soap"; > xmlns:impl="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; > xmlns:intf="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; > xmlns:tns1="http://webservice.psr.datamigration.ch"; > xmlns:tns2="http://www.data-migration.ch/"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > > >targetNamespace="http://webservice.psr.datamigration.ch"; > xmlns="http://www.w3.org/2001/XMLSchema";> >http://www.data-migration.ch/"/> > > > > > > > > > > > > > > > >targetNamespace="http://www.data-migration.ch/"; > xmlns="http://www.w3.org/2001/XMLSchema";> > > > > > > > > > > > > > > > > > > > > name="getBookByISBNRequest"/> > name="getBookByISBNResponse"/> > > > type="impl:BookController"> >transport="http://schemas.xmlsoap.org/soap/http"/> > > > > > > > > > > > >name="AxisBookWrappedLiteral"> > location="http://192.168.155.254:8080/axis/services/AxisBookWrappedLiteral"/> > > > > > The Soap Request: > > > targetNamespace="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; > xmlns:apachesoap="http://xml.apache.org/xml-soap"; > xmlns:impl="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; > xmlns:intf="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; > xmlns:tns1="http://webservice.psr.datamigration.ch"; > xmlns:tns2="http://www.data-migration.ch/"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > > >targetNamespace="http://webservice.psr.datamigration.ch"; > xmlns="http://www.w3.org/2001/XMLSchema";> >http://www.data-migration.ch/"/> > > > > > > > > > > > > > > > >targetNamespace="http://www.data-migration.ch/"; > xmlns="http://www.w3.org/2001/XMLSchema";> > > > > > > > > > > > > > > > > > > > > name="getBookByISBNRequest"/> > name="getBookByISBNResponse"/> > > > type="impl:BookController"> >transport="http://schemas.xmlsoap.org/soap/http"/> > >
Re: Axis 1.4 server -> .NET 2.0 client - Doc/Literal namespace? trouble
There's a namespace error in the response message. According to the WSDL, the response message should look like this (or the semantic equivalent): http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> http://webservice.psr.datamigration.ch";> http://www.data-migration.ch/";> Dan Diephouse 0123456789 2006-10-16T14:10:39.796Z Mon Oct 16 16:10:39 CEST 2006 Using XFire Anne On 10/16/06, Philipp Stader <[EMAIL PROTECTED]> wrote: Thank you very much for your reply! On 10/15/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > How did you generate the WSDL? > (The WSDL and the response message don't match.) > > For best result, generate a wrapped style service. I am using wrapped/literal now. The Wsdl is generated through Axis "on-the-fly". Maybe i mixed something up compiling the mail. Here is what i am testing with right now. When calling getBookByISBN the Book Object gets instantiated by .NET but all properties are null. Same Java class files using XFire as Soap Stack work for me. I will try Axis 2 1.1 too but we have quite some installations using Axis 1.4 and would like to keep it for now. deploy.wsdd, wsdl generated by Axis and Soap Request / Response to follow. Axis 1.4 is deployed on a Tomcat 4.1.31 using Java SDK 1.4.2_12 deploy.wsdd for Axis http://xml.apache.org/axis/wsdd/"; xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"; xmlns:dmns="http://www.data-migration.ch/";> The wsdl Axis generates looks like this: http://localhost:8080/axis/services/AxisBookWrappedLiteral"; xmlns:apachesoap="http://xml.apache.org/xml-soap"; xmlns:impl="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; xmlns:intf="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; xmlns:tns1="http://webservice.psr.datamigration.ch"; xmlns:tns2="http://www.data-migration.ch/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> http://webservice.psr.datamigration.ch"; xmlns="http://www.w3.org/2001/XMLSchema";> http://www.data-migration.ch/"/> http://www.data-migration.ch/"; xmlns="http://www.w3.org/2001/XMLSchema";> http://schemas.xmlsoap.org/soap/http"/> http://192.168.155.254:8080/axis/services/AxisBookWrappedLiteral"/> The Soap Request: http://localhost:8080/axis/services/AxisBookWrappedLiteral"; xmlns:apachesoap="http://xml.apache.org/xml-soap"; xmlns:impl="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; xmlns:intf="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; xmlns:tns1="http://webservice.psr.datamigration.ch"; xmlns:tns2="http://www.data-migration.ch/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> http://webservice.psr.datamigration.ch"; xmlns="http://www.w3.org/2001/XMLSchema";> http://www.data-migration.ch/"/> http://www.data-migration.ch/"; xmlns="http://www.w3.org/2001/XMLSchema";> http://schemas.xmlsoap.org/soap/http"/> http://192.168.155.254:8080/axis/services/AxisBookWrappedLiteral"/> The Response by Axis which .NET 2.0 fails to parse. All properties of the Book Object returned by a call to getBookByISBN are null. The response shows the data is there and i am lost. http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> http://webservice.psr.datamigration.ch";> Dan Diephouse 0123456789 2006-10-16T14:10:39.796Z Mon Oct 16 16:10:39 CEST 2006 Using XFire > Anne > > On 10/12/06, Philipp Stader <[EMAIL PROTECTED]> wrote: > > Hi there, > > > > lucky me has to write a .NET 2.0 client to consume Axis Web Services. > > Right now all Web Services are deployed using Rpc/Encoded. Doing some > > quick research it sounds like Document/Literal is the way to go. The > > rpc/enc se
Re: Axis 1.4 server -> .NET 2.0 client - Doc/Literal namespace? trouble
Thank you very much for your reply! On 10/15/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: How did you generate the WSDL? (The WSDL and the response message don't match.) For best result, generate a wrapped style service. I am using wrapped/literal now. The Wsdl is generated through Axis "on-the-fly". Maybe i mixed something up compiling the mail. Here is what i am testing with right now. When calling getBookByISBN the Book Object gets instantiated by .NET but all properties are null. Same Java class files using XFire as Soap Stack work for me. I will try Axis 2 1.1 too but we have quite some installations using Axis 1.4 and would like to keep it for now. deploy.wsdd, wsdl generated by Axis and Soap Request / Response to follow. Axis 1.4 is deployed on a Tomcat 4.1.31 using Java SDK 1.4.2_12 deploy.wsdd for Axis http://xml.apache.org/axis/wsdd/"; xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"; xmlns:dmns="http://www.data-migration.ch/";> The wsdl Axis generates looks like this: http://localhost:8080/axis/services/AxisBookWrappedLiteral"; xmlns:apachesoap="http://xml.apache.org/xml-soap"; xmlns:impl="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; xmlns:intf="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; xmlns:tns1="http://webservice.psr.datamigration.ch"; xmlns:tns2="http://www.data-migration.ch/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> http://webservice.psr.datamigration.ch"; xmlns="http://www.w3.org/2001/XMLSchema";> http://www.data-migration.ch/"/> http://www.data-migration.ch/"; xmlns="http://www.w3.org/2001/XMLSchema";> http://schemas.xmlsoap.org/soap/http"/> http://192.168.155.254:8080/axis/services/AxisBookWrappedLiteral"/> The Soap Request: http://localhost:8080/axis/services/AxisBookWrappedLiteral"; xmlns:apachesoap="http://xml.apache.org/xml-soap"; xmlns:impl="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; xmlns:intf="http://localhost:8080/axis/services/AxisBookWrappedLiteral"; xmlns:tns1="http://webservice.psr.datamigration.ch"; xmlns:tns2="http://www.data-migration.ch/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> http://webservice.psr.datamigration.ch"; xmlns="http://www.w3.org/2001/XMLSchema";> http://www.data-migration.ch/"/> http://www.data-migration.ch/"; xmlns="http://www.w3.org/2001/XMLSchema";> http://schemas.xmlsoap.org/soap/http"/> http://192.168.155.254:8080/axis/services/AxisBookWrappedLiteral"/> The Response by Axis which .NET 2.0 fails to parse. All properties of the Book Object returned by a call to getBookByISBN are null. The response shows the data is there and i am lost. http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> http://webservice.psr.datamigration.ch";> Dan Diephouse 0123456789 2006-10-16T14:10:39.796Z Mon Oct 16 16:10:39 CEST 2006 Using XFire Anne On 10/12/06, Philipp Stader <[EMAIL PROTECTED]> wrote: > Hi there, > > lucky me has to write a .NET 2.0 client to consume Axis Web Services. > Right now all Web Services are deployed using Rpc/Encoded. Doing some > quick research it sounds like Document/Literal is the way to go. The > rpc/enc services get consumed quite ok, unfortunately .NET has an > issue talking to an Axis Document/Literal Service i created. > Interestingly enough it is able to work with an XFire Document/Literal > Web Service fine based on the very same (basic) Java classes. There is > a difference in the response to the requests by the two and apparently > the change is big enough to make .NET struggle. > > Response by Axis: > > > http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > >http://webservice.psr.datamigration.ch";> >Dan Diephouse >0123456789 > > 2006-10-1
Re: Axis 1.4 server -> .NET 2.0 client - Doc/Literal namespace? trouble
How did you generate the WSDL? (The WSDL and the response message don't match.) For best result, generate a wrapped style service. Anne On 10/12/06, Philipp Stader <[EMAIL PROTECTED]> wrote: Hi there, lucky me has to write a .NET 2.0 client to consume Axis Web Services. Right now all Web Services are deployed using Rpc/Encoded. Doing some quick research it sounds like Document/Literal is the way to go. The rpc/enc services get consumed quite ok, unfortunately .NET has an issue talking to an Axis Document/Literal Service i created. Interestingly enough it is able to work with an XFire Document/Literal Web Service fine based on the very same (basic) Java classes. There is a difference in the response to the requests by the two and apparently the change is big enough to make .NET struggle. Response by Axis: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> http://webservice.psr.datamigration.ch";> Dan Diephouse 0123456789 2006-10-11T14:06:37.656Z Wed Oct 11 16:06:37 CEST 2006 Using XFire Response by XFire: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> http://localhost:8080/xfire/services/BookController";> http://webservice.psr.datamigration.ch";> Dan Diephouse http://webservice.psr.datamigration.ch";>0123456789 http://webservice.psr.datamigration.ch";> 2006-10-11T16:08:01.484+02:00 http://webservice.psr.datamigration.ch";> Wed Oct 11 16:08:01 CEST 2006 http://webservice.psr.datamigration.ch";>Using XFire The XFire Response is happily accepted by the .NET 2.0 client using the proxy class generated by Add Web Reference. I have no clue how to bribe Axis to send a Doc/Literal answer that .NET is able to parse (and if i really would want to). Also don't know if XFire is doing something "wrong" just to please the .NET clients out there. Another thing i tried was to take the wsdl generated by XFire (since "it" works) to again generate wsdd (WSDL2Java) for Axis. Didn't make a difference for my tests. (i know i should do WSDL first but this isn't feasible for my current task). I also changed the to false. Didn't change anything. I also tried with the wrapped style but no go also. All hints and pointers highly appreciated. I'll be more than happy to document what it takes to make Axis Doc/Lit work with .NET 2.0 on the wiki. Seems like all docs there target .NET 1.0/1.1 Phil WSDLs, Deployment Descriptors to follow: WSDL generated by Axis: http://localhost:8080/axis/services/BookControllerDocLiteral"; xmlns:apachesoap="http://xml.apache.org/xml-soap"; xmlns:impl="http://localhost:8080/axis/services/BookControllerDocLiteral"; xmlns:intf="http://localhost:8080/axis/services/BookControllerDocLiteral"; xmlns:tns1="http://www.data-migration.ch/"; xmlns:tns2="http://webservice.psr.datamigration.ch"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> http://www.data-migration.ch/"; xmlns="http://www.w3.org/2001/XMLSchema";> http://localhost:8080/axis/services/BookControllerDocLiteral"; xmlns="http://www.w3.org/2001/XMLSchema";> http://www.data-migration.ch/"/> http://webservice.psr.datamigration.ch"; xmlns="http://www.w3.org/2001/XMLSchema";> http://www.data-migration.ch/"/> http://schemas.xmlsoap.org/soap/http"/> http://localhost:8080/axis/services/BookControllerDocLiteral"/> Wsdl by XFire http://localhost:8080/xfire/services/BookController"; xmlns:tns="http://localhost:8080/xfire/services/BookController"; xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:soap12="http://www.w3.org/2003/05/soap-envelope"; xmlns:ns1="http://webservice.psr.datamigration.ch"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:soapenc11="http://schemas.xmlsoap.o
Axis 1.4 server -> .NET 2.0 client - Doc/Literal namespace? trouble
Hi there, lucky me has to write a .NET 2.0 client to consume Axis Web Services. Right now all Web Services are deployed using Rpc/Encoded. Doing some quick research it sounds like Document/Literal is the way to go. The rpc/enc services get consumed quite ok, unfortunately .NET has an issue talking to an Axis Document/Literal Service i created. Interestingly enough it is able to work with an XFire Document/Literal Web Service fine based on the very same (basic) Java classes. There is a difference in the response to the requests by the two and apparently the change is big enough to make .NET struggle. Response by Axis: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> http://webservice.psr.datamigration.ch";> Dan Diephouse 0123456789 2006-10-11T14:06:37.656Z Wed Oct 11 16:06:37 CEST 2006 Using XFire Response by XFire: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> http://localhost:8080/xfire/services/BookController";> http://webservice.psr.datamigration.ch";> Dan Diephouse http://webservice.psr.datamigration.ch";>0123456789 http://webservice.psr.datamigration.ch";> 2006-10-11T16:08:01.484+02:00 http://webservice.psr.datamigration.ch";> Wed Oct 11 16:08:01 CEST 2006 http://webservice.psr.datamigration.ch";>Using XFire The XFire Response is happily accepted by the .NET 2.0 client using the proxy class generated by Add Web Reference. I have no clue how to bribe Axis to send a Doc/Literal answer that .NET is able to parse (and if i really would want to). Also don't know if XFire is doing something "wrong" just to please the .NET clients out there. Another thing i tried was to take the wsdl generated by XFire (since "it" works) to again generate wsdd (WSDL2Java) for Axis. Didn't make a difference for my tests. (i know i should do WSDL first but this isn't feasible for my current task). I also changed the to false. Didn't change anything. I also tried with the wrapped style but no go also. All hints and pointers highly appreciated. I'll be more than happy to document what it takes to make Axis Doc/Lit work with .NET 2.0 on the wiki. Seems like all docs there target .NET 1.0/1.1 Phil WSDLs, Deployment Descriptors to follow: WSDL generated by Axis: http://localhost:8080/axis/services/BookControllerDocLiteral"; xmlns:apachesoap="http://xml.apache.org/xml-soap"; xmlns:impl="http://localhost:8080/axis/services/BookControllerDocLiteral"; xmlns:intf="http://localhost:8080/axis/services/BookControllerDocLiteral"; xmlns:tns1="http://www.data-migration.ch/"; xmlns:tns2="http://webservice.psr.datamigration.ch"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> http://www.data-migration.ch/"; xmlns="http://www.w3.org/2001/XMLSchema";> http://localhost:8080/axis/services/BookControllerDocLiteral"; xmlns="http://www.w3.org/2001/XMLSchema";> http://www.data-migration.ch/"/> http://webservice.psr.datamigration.ch"; xmlns="http://www.w3.org/2001/XMLSchema";> http://www.data-migration.ch/"/> http://schemas.xmlsoap.org/soap/http"/> http://localhost:8080/axis/services/BookControllerDocLiteral"/> Wsdl by XFire http://localhost:8080/xfire/services/BookController"; xmlns:tns="http://localhost:8080/xfire/services/BookController"; xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:soap12="http://www.w3.org/2003/05/soap-envelope"; xmlns:ns1="http://webservice.psr.datamigration.ch"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:soapenc11="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:soapenc12="http://www.w3.org/2003/05/soap-encoding"; xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";> http://webservice.psr.datamigration.ch"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> http://localhost:8080/xfire/services/BookContro
