Re: array serialization in 1.3
I'm a bit swamped at the moment and don't have time to help you right now -- sorry.On 3/28/06, Marc Brette <[EMAIL PROTECTED] > wrote:Hi Anne,Do you also need the complete WSDL and XSD files?I can send them if needed. --- Marc Brette <[EMAIL PROTECTED]> a écrit :> Here it is:> > > > > > > > > > > > >> > > > minOccurs="0" default="en-US">> > > Optional locale indicating language of > request.> Used when it is> necessary to distinguish> language of certain elements in the request> parameters (search terms,> source > selection, etc.)> > > > > >> --- Anne Thomas Manes <[EMAIL PROTECTED]> a écrit :>> > Please also provide the tyoe definition of> > common:BaseRequest.> > > > On 3/20/06, Marc Brette <[EMAIL PROTECTED]> wrote:> > >> > > Here it is. It is quite complex because there> are> > > dozens of operation and .xsd inclusion, so I > just> > > extracted the relevant data structures (I can> > provide> > > the whole WSDL if needed).> > >> > > WSDL:> > > [...]> > > > > >> >>namespace="http://search.search.services.v1.wsapi.lexisnexis.com"> > > schemaLocation=" Search.xsd"/>> > > [...]> > > > > > > > > name="SearchRequest"/> > > > > > > > > > > > element="search-search:SearchResponse"> > > name="SearchResponse"/> > > > > > > [...]> > > > > > > > > > > message="tns:Search-SearchReqMsg"/>> > > > > message="tns:Search-SearchRespMsg"/>> > > > > > > > > [...]> > > > > > type="tns:SearchSoapPort">> > > > > >> transport="http://schemas.xmlsoap.org/soap/http"/>> > > > > > > soapAction=""/>> > > > > > > > use="literal"/>> > > > > > > > > > > use="literal"/>> > > > > > > > > > > > > soapAction=""/>> > > > > > > > use="literal"/>> > > > > > > > > > > use="literal"/> > > > > > > > > > > > > [...]> > >> > >> > > Search.xsd: > > > > > > http://www.w3.org/2001/XMLSchema"> > > > > >> >>targetNamespace="http://search.search.services.v1.wsapi.lexisnexis.com"> > >> > > > >>xmlns:tns="http://search.search.services.v1.wsapi.lexisnexis.com"> > >> > >> > >xmlns:common="http://common.services.v1.wsapi.lexisnexis.com"> > >> > >> >>xmlns:result=" http://result.common.services.v1.wsapi.lexisnexis.com"> > >> > >> >>xmlns:searchcommon="http://common.search.services.v1.wsapi.lexisnexis.com "> > >> > >> >>xmlns:security="http://security.common.services.v1.wsapi.lexisnexis.com" > > > elementFormDefault="qualified"> > > attributeFormDefault="unqualified"> > > version="1.0">> > >> > > > > >> >>namespace="http://common.services.v1.wsapi.lexisnexis.com"> > > schemaLocation=" Common.xsd"/>> > > > > >> >>namespace="http://result.common.services.v1.wsapi.lexisnexis.com "> > > schemaLocation="Result.xsd"/>> > > > > >> >>namespace=" http://common.search.services.v1.wsapi.lexisnexis.com"> > > schemaLocation="SearchCommon.xsd"/>> > > > > >> >>namespace=" http://security.common.services.v1.wsapi.lexisnexis.com"> > > schemaLocation="Security.xsd"/>> > > > > > > > > > > > > > > > > > Represents a LexisNexis search and> > retrieval.> > > Many options are> > > exposed to allow a user to customize the> > > search request. > > > > > > > > > > > >> > > > > > type="result:SearchResponse"> > > > > > > > > > The response from a search request is a> > set of> > > search results,> > > containing document identifiers along > with> > > documents in the> > > specified or default output format.> > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > name="binarySecurityToken"> > > type="security:BinarySecurityToken">> > > > > > > > >> > >> f4348ad8876542bc93748c89fb98a7e>=== message truncated === ___Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com
Re: array serialization in 1.3
Hi Anne, Do you also need the complete WSDL and XSD files? I can send them if needed. --- Marc Brette <[EMAIL PROTECTED]> a écrit : > Here it is: > > > > > > > > > > > > > > > >minOccurs="0" default="en-US"> > > > Optional locale indicating language of > request. > Used when it is > necessary to distinguish > language of certain elements in the request > parameters (search terms, > source > selection, etc.) > > > > > > > --- Anne Thomas Manes <[EMAIL PROTECTED]> a écrit : > > > Please also provide the tyoe definition of > > common:BaseRequest. > > > > On 3/20/06, Marc Brette <[EMAIL PROTECTED]> wrote: > > > > > > Here it is. It is quite complex because there > are > > > dozens of operation and .xsd inclusion, so I > just > > > extracted the relevant data structures (I can > > provide > > > the whole WSDL if needed). > > > > > > WSDL: > > > [...] > > > > > > > > namespace="http://search.search.services.v1.wsapi.lexisnexis.com"; > > > schemaLocation="Search.xsd"/> > > > [...] > > > > > > > > name="SearchRequest"/> > > > > > > > > > > element="search-search:SearchResponse" > > > name="SearchResponse"/> > > > > > > [...] > > > > > > > > > > message="tns:Search-SearchReqMsg"/> > > > > message="tns:Search-SearchRespMsg"/> > > > > > > > > > [...] > > > > > type="tns:SearchSoapPort"> > > > > > > transport="http://schemas.xmlsoap.org/soap/http"/> > > > > > > soapAction=""/> > > > > > > > use="literal"/> > > > > > > > > > > use="literal"/> > > > > > > > > > > > > soapAction=""/> > > > > > > > use="literal"/> > > > > > > > > > > use="literal"/> > > > > > > > > > > > > [...] > > > > > > > > > Search.xsd: > > > > > > http://www.w3.org/2001/XMLSchema"; > > > > > > > > > targetNamespace="http://search.search.services.v1.wsapi.lexisnexis.com"; > > > > > > > > > xmlns:tns="http://search.search.services.v1.wsapi.lexisnexis.com"; > > > > > > > > > xmlns:common="http://common.services.v1.wsapi.lexisnexis.com"; > > > > > > > > > xmlns:result="http://result.common.services.v1.wsapi.lexisnexis.com"; > > > > > > > > > xmlns:searchcommon="http://common.search.services.v1.wsapi.lexisnexis.com"; > > > > > > > > > xmlns:security="http://security.common.services.v1.wsapi.lexisnexis.com"; > > > elementFormDefault="qualified" > > > attributeFormDefault="unqualified" > > > version="1.0"> > > > > > >> > > > > namespace="http://common.services.v1.wsapi.lexisnexis.com"; > > > schemaLocation="Common.xsd"/> > > >> > > > > namespace="http://result.common.services.v1.wsapi.lexisnexis.com"; > > > schemaLocation="Result.xsd"/> > > >> > > > > namespace="http://common.search.services.v1.wsapi.lexisnexis.com"; > > > schemaLocation="SearchCommon.xsd"/> > > >> > > > > namespace="http://security.common.services.v1.wsapi.lexisnexis.com"; > > > schemaLocation="Security.xsd"/> > > > > > > > > > > > > > > > > > > Represents a LexisNexis search and > > retrieval. > > > Many options are > > > exposed to allow a user to customize the > > > search request. > > > > > > > > > > > > > > >> > type="result:SearchResponse"> > > > > > > > > > The response from a search request is a > > set of > > > search results, > > > containing document identifiers along > with > > > documents in the > > > specified or default output format. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >name="binarySecurityToken" > > > type="security:BinarySecurityToken"> > > > > > > > > > > > > > f4348ad8876542bc93748c89fb98a7e > === message truncated === ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com
Re: array serialization in 1.3
Here it is: Optional locale indicating language of request. Used when it is necessary to distinguish language of certain elements in the request parameters (search terms, source selection, etc.) --- Anne Thomas Manes <[EMAIL PROTECTED]> a écrit : > Please also provide the tyoe definition of > common:BaseRequest. > > On 3/20/06, Marc Brette <[EMAIL PROTECTED]> wrote: > > > > Here it is. It is quite complex because there are > > dozens of operation and .xsd inclusion, so I just > > extracted the relevant data structures (I can > provide > > the whole WSDL if needed). > > > > WSDL: > > [...] > > > > namespace="http://search.search.services.v1.wsapi.lexisnexis.com"; > > schemaLocation="Search.xsd"/> > > [...] > > > > > name="SearchRequest"/> > > > > > > element="search-search:SearchResponse" > > name="SearchResponse"/> > > > > [...] > > > > > > message="tns:Search-SearchReqMsg"/> > > message="tns:Search-SearchRespMsg"/> > > > > > > [...] > > > type="tns:SearchSoapPort"> > > > transport="http://schemas.xmlsoap.org/soap/http"/> > > > > > > > > use="literal"/> > > > > > > use="literal"/> > > > > > > > > > > > > use="literal"/> > > > > > > use="literal"/> > > > > > > > > [...] > > > > > > Search.xsd: > > > > http://www.w3.org/2001/XMLSchema"; > > > > > targetNamespace="http://search.search.services.v1.wsapi.lexisnexis.com"; > > > > > xmlns:tns="http://search.search.services.v1.wsapi.lexisnexis.com"; > > > > > xmlns:common="http://common.services.v1.wsapi.lexisnexis.com"; > > > > > xmlns:result="http://result.common.services.v1.wsapi.lexisnexis.com"; > > > > > xmlns:searchcommon="http://common.search.services.v1.wsapi.lexisnexis.com"; > > > > > xmlns:security="http://security.common.services.v1.wsapi.lexisnexis.com"; > > elementFormDefault="qualified" > > attributeFormDefault="unqualified" > > version="1.0"> > > > >> > namespace="http://common.services.v1.wsapi.lexisnexis.com"; > > schemaLocation="Common.xsd"/> > >> > namespace="http://result.common.services.v1.wsapi.lexisnexis.com"; > > schemaLocation="Result.xsd"/> > >> > namespace="http://common.search.services.v1.wsapi.lexisnexis.com"; > > schemaLocation="SearchCommon.xsd"/> > >> > namespace="http://security.common.services.v1.wsapi.lexisnexis.com"; > > schemaLocation="Security.xsd"/> > > > > > > > > > > > > Represents a LexisNexis search and > retrieval. > > Many options are > > exposed to allow a user to customize the > > search request. > > > > > > > > > >> type="result:SearchResponse"> > > > > > > The response from a search request is a > set of > > search results, > > containing document identifiers along with > > documents in the > > specified or default output format. > > > > > > > > > > > > > > > > > > > >> type="security:BinarySecurityToken"> > > > > > > > > f4348ad8876542bc93748c89fb98a7e > > Security token that must be > provided on > > all non-authentication > > requests. > > > > > > > >> type="searchcommon:SourceInformationChoice"> > > > > > >Either a list of source > identifiers or > > a single secured > > source identifier. > > > > > > > > > > > > > > cats and dogs and > > hamsters > > Query string for the search > request, > > formatted in the > > appropriate syntax for the > selected > > search method. > > > > > > > >> type="common:ProjectId" minOccurs="0"> > > > > > > Research Project > 001 > > Used for client or project > identification > > purposes. This > > identi
Re: array serialization in 1.3
Please also provide the tyoe definition of common:BaseRequest.On 3/20/06, Marc Brette <[EMAIL PROTECTED]> wrote: Here it is. It is quite complex because there aredozens of operation and .xsd inclusion, so I just extracted the relevant data structures (I can providethe whole WSDL if needed).WSDL:[...]namespace="http://search.search.services.v1.wsapi.lexisnexis.com "schemaLocation="Search.xsd"/>[...]name="SearchRequest"/> name="SearchResponse"/>[...] [...]type="tns:SearchSoapPort">transport=" http://schemas.xmlsoap.org/soap/http"/> [...]Search.xsd: http://www.w3.org/2001/XMLSchema"targetNamespace="http://search.search.services.v1.wsapi.lexisnexis.com "xmlns:tns="http://search.search.services.v1.wsapi.lexisnexis.com"xmlns:common=" http://common.services.v1.wsapi.lexisnexis.com"xmlns:result="http://result.common.services.v1.wsapi.lexisnexis.com"xmlns:searchcommon=" http://common.search.services.v1.wsapi.lexisnexis.com"xmlns:security=" http://security.common.services.v1.wsapi.lexisnexis.com"elementFormDefault="qualified"attributeFormDefault="unqualified"version="1.0"> namespace="http://common.services.v1.wsapi.lexisnexis.com" schemaLocation="Common.xsd"/> namespace=" http://result.common.services.v1.wsapi.lexisnexis.com" schemaLocation="Result.xsd"/> namespace=" http://common.search.services.v1.wsapi.lexisnexis.com" schemaLocation="SearchCommon.xsd"/> namespace=" http://security.common.services.v1.wsapi.lexisnexis.com" schemaLocation="Security.xsd"/> Represents a LexisNexis search and retrieval.Many options areexposed to allow a user to customize thesearch request. type="result:SearchResponse"> The response from a search request is a set of search results,containing document identifiers along withdocuments in thespecified or default output format. type="security:BinarySecurityToken"> f4348ad8876542bc93748c89fb98a7eSecurity token that must be provided on all non-authenticationrequests. type="searchcommon:SourceInformationChoice"> Either a list of source identifiers ora single secured source identifier. cats and dogs andhamsters Query string for the search request, formatted in the appropriate syntax for the selectedsearch method. type="common:ProjectId" minOccurs="0"> Research Project 001 Used for client or project identificationpurposes. Thisidentifier will be associated with eachsearch transactionand will be reported on your organization's invoice. type="searchcommon:SearchOptions" minOccurs="0"> Options pertaining to fine-tuning thesearch. type="result:RetrievalOptions" minOccurs="0"> Options pertaining to the view, markup,and range of documents retrieved fromthe result set returned from the search. SearchCommon.xsd:http://www.w3.org/2001/XMLSchema"targetNamespace=" http://common.search.services.v1.wsapi.lexisnexis.com"xmlns:tns="http://common.search.services.v1.wsapi.lexisnexis.com" xmlns:result="http://result.common.services.v1.wsapi.lexisnexis.com"xmlns:common=" http://common.services.v1.wsapi.lexisnexis.com"elementFormDefault="qualified"attributeFormDefault="unqualified"version="1.0"> namespace="http://result.common.services.v1.wsapi.lexisnexis.com"schemaLocation="Result.xsd"/> namespace="http://common.services.v1.wsapi.lexisnexis.com"schemaLocation="Common.xsd"/> type="common:SourceIdList" minOccurs="0"> A grouping of LexisNexis sources.Mutually exclusive ofthe securedSourceId element. minOccurs="0"> Unique identifier for a "s
Re: array serialization in 1.3
Here it is. It is quite complex because there are dozens of operation and .xsd inclusion, so I just extracted the relevant data structures (I can provide the whole WSDL if needed). WSDL: [...] http://search.search.services.v1.wsapi.lexisnexis.com"; schemaLocation="Search.xsd"/> [...] [...] [...] http://schemas.xmlsoap.org/soap/http"/> [...] Search.xsd: http://www.w3.org/2001/XMLSchema"; targetNamespace="http://search.search.services.v1.wsapi.lexisnexis.com"; xmlns:tns="http://search.search.services.v1.wsapi.lexisnexis.com"; xmlns:common="http://common.services.v1.wsapi.lexisnexis.com"; xmlns:result="http://result.common.services.v1.wsapi.lexisnexis.com"; xmlns:searchcommon="http://common.search.services.v1.wsapi.lexisnexis.com"; xmlns:security="http://security.common.services.v1.wsapi.lexisnexis.com"; elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0"> http://common.services.v1.wsapi.lexisnexis.com"; schemaLocation="Common.xsd"/> http://result.common.services.v1.wsapi.lexisnexis.com"; schemaLocation="Result.xsd"/> http://common.search.services.v1.wsapi.lexisnexis.com"; schemaLocation="SearchCommon.xsd"/> http://security.common.services.v1.wsapi.lexisnexis.com"; schemaLocation="Security.xsd"/> Represents a LexisNexis search and retrieval. Many options are exposed to allow a user to customize the search request. The response from a search request is a set of search results, containing document identifiers along with documents in the specified or default output format. f4348ad8876542bc93748c89fb98a7e Security token that must be provided on all non-authentication requests. Either a list of source identifiers or a single secured source identifier. cats and dogs and hamsters Query string for the search request, formatted in the appropriate syntax for the selected search method. Research Project 001 Used for client or project identification purposes. This identifier will be associated with each search transaction and will be reported on your organization's invoice. Options pertaining to fine-tuning the search. Options pertaining to the view, markup, and range of documents retrieved from the result set returned from the search. SearchCommon.xsd: http://www.w3.org/2001/XMLSchema"; targetNamespace="http://common.search.services.v1.wsapi.lexisnexis.com"; xmlns:tns="http://common.search.services.v1.wsapi.lexisnexis.com"; xmlns:result="http://result.common.services.v1.wsapi.lexisnexis.com"; xmlns:common="http://common.services.v1.wsapi.lexisnexis.com"; elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0"> http://result.common.services.v1.wsapi.lexisnexis.com"; schemaLocation="Result.xsd"/> http://common.services.v1.wsapi.lexisnexis.com"; schemaLocation="Common.xsd"/> A grouping of LexisNexis sources. Mutually exclusive of the securedSourceId element. Unique identifier for a "secured" LexisNexis source. Mutually exclusive of the sourceIdList element. [...] Common.xsd: http://www.w3.org/2001/XMLSchema"; targetNamespace="http://common.services.v1.wsapi.lexisnexis.com"; xmlns:tns="http
Re: array serialization in 1.3
Would you please supply the rest of the WSDL? (or at least the bits that describe the message and element structure)AnneOn 3/16/06, Marc Brette <[EMAIL PROTECTED]> wrote:Then this may not be the same issue. The binding is defined as follow:type="tns:SearchSoapPort"> transport=" http://schemas.xmlsoap.org/soap/http"/> See below the axis 1.1 request (that works) and theaxis 1.3 request:1.1: (I cut some part for simplicity sake)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"> xmlns=" http://search.search.services.v1.wsapi.lexisnexis.com"> [...] xmlns:ns1=" http://common.search.services.v1.wsapi.lexisnexis.com"> xmlns:ns2="http://common.services.v1.wsapi.lexisnexis.com">274668 [...] [...] [...] [...] 1.3 (look at the difference in the sourceIdList tag) 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"> xmlns=" http://search.search.services.v1.wsapi.lexisnexis.com"> [...] xmlns:ns1="http://common.search.services.v1.wsapi.lexisnexis.com">274668 [...] [...] [...] [...] --- Anne Thomas Manes <[EMAIL PROTECTED]> a écrit :> Sorry -- that was a typo:>> You *cannot* use soapenc:array or SOAP encoding with > use="literal".>> Anne>> On 3/15/06, Dies Koper <[EMAIL PROTECTED]> wrote:> >> > Hello Anne,> > > > Recently, I noticed a few issues with WSDL files> that used soapenc:array> > or simple types such as soapenc:int with> use=literal. What are the> > consequences of this mixing? What should be > happening?> >> > For example, the JAX-RPC specification says that> all soapenc types are> > nillable. Does that mean > type="soapenc:int" nillable="false"/> > > still maps to Integer (not int)? Or only when> use="encoded"?> >> > > http://schemas.xmlsoap.org/soap/encoding/"> > >> namespace="http://demo.radialpoint.com/service"> use="literal" /> > > >> > > It should say:> > >> > > http://schemas.xmlsoap.org/soap/encoding/ "> > >> namespace="http://demo.radialpoint.com/service"> use="encoded" />> > >> > > You can use soapenc:array or SOAP encoding with > use="literal".> >> > If you can, does that mean that Erik could also> fix it like this?> >> > > namespace=" http://demo.radialpoint.com/service"> > use="literal" />> >> > Thanks,> > Dies> >> >>___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international.Téléchargez sur http://fr.messenger.yahoo.com
Re: array serialization in 1.3
Then this may not be the same issue. The binding is defined as follow: http://schemas.xmlsoap.org/soap/http"/> See below the axis 1.1 request (that works) and the axis 1.3 request: 1.1: (I cut some part for simplicity sake) http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> http://search.search.services.v1.wsapi.lexisnexis.com";> [...] http://common.search.services.v1.wsapi.lexisnexis.com";> http://common.services.v1.wsapi.lexisnexis.com";>274668 [...] [...] [...] [...] 1.3 (look at the difference in the sourceIdList tag) http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> http://search.search.services.v1.wsapi.lexisnexis.com";> [...] http://common.search.services.v1.wsapi.lexisnexis.com";>274668 [...] [...] [...] [...] --- Anne Thomas Manes <[EMAIL PROTECTED]> a écrit : > Sorry -- that was a typo: > > You *cannot* use soapenc:array or SOAP encoding with > use="literal". > > Anne > > On 3/15/06, Dies Koper <[EMAIL PROTECTED]> wrote: > > > > Hello Anne, > > > > Recently, I noticed a few issues with WSDL files > that used soapenc:array > > or simple types such as soapenc:int with > use=literal. What are the > > consequences of this mixing? What should be > happening? > > > > For example, the JAX-RPC specification says that > all soapenc types are > > nillable. Does that mean type="soapenc:int" nillable="false"/> > > still maps to Integer (not int)? Or only when > use="encoded"? > > > > > http://schemas.xmlsoap.org/soap/encoding/"; > > > > namespace="http://demo.radialpoint.com/service"; > use="literal" /> > > > > > > It should say: > > > > > > http://schemas.xmlsoap.org/soap/encoding/"; > > > > namespace="http://demo.radialpoint.com/service"; > use="encoded" /> > > > > > > You can use soapenc:array or SOAP encoding with > use="literal". > > > > If you can, does that mean that Erik could also > fix it like this? > > > > namespace="http://demo.radialpoint.com/service"; > > use="literal" /> > > > > Thanks, > > Dies > > > > > ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com
Re: array serialization in 1.3
Sorry -- that was a typo:You *cannot* use soapenc:array or SOAP encoding with use="literal".AnneOn 3/15/06, Dies Koper <[EMAIL PROTECTED]> wrote: Hello Anne,Recently, I noticed a few issues with WSDL files that used soapenc:arrayor simple types such as soapenc:int with use=literal. What are theconsequences of this mixing? What should be happening? For example, the JAX-RPC specification says that all soapenc types arenillable. Does that mean still maps to Integer (not int)? Or only when use="encoded"? > http://schemas.xmlsoap.org/soap/encoding/"> namespace=" http://demo.radialpoint.com/service" use="literal" />>> It should say:>> http://schemas.xmlsoap.org/soap/encoding/ "> namespace="http://demo.radialpoint.com/service" use="encoded" />>> You can use soapenc:array or SOAP encoding with use="literal". If you can, does that mean that Erik could also fix it like this?http://demo.radialpoint.com/service"use="literal" /> Thanks,Dies
Re: array serialization in 1.3
Hello Anne, Recently, I noticed a few issues with WSDL files that used soapenc:array or simple types such as soapenc:int with use=literal. What are the consequences of this mixing? What should be happening? For example, the JAX-RPC specification says that all soapenc types are nillable. Does that mean still maps to Integer (not int)? Or only when use="encoded"? http://schemas.xmlsoap.org/soap/encoding/"; namespace="http://demo.radialpoint.com/service"; use="literal" /> It should say: http://schemas.xmlsoap.org/soap/encoding/"; namespace="http://demo.radialpoint.com/service"; use="encoded" /> You can use soapenc:array or SOAP encoding with use="literal". If you can, does that mean that Erik could also fix it like this? http://demo.radialpoint.com/service"; use="literal" /> Thanks, Dies
Re: array serialization in 1.3
In Erik's binding it says: http://schemas.xmlsoap.org/soap/encoding/ " namespace="http://demo.radialpoint.com/service" use="literal" /> It should say: http://schemas.xmlsoap.org/soap/encoding/ " namespace="http://demo.radialpoint.com/service" use="encoded" /> You can use soapenc:array or SOAP encoding with use="literal".AnneOn 3/15/06, Marc Brette < [EMAIL PROTECTED]> wrote:Hi all,I seem to run in the same issue as Erik. I have an Axis client that sends incorrectlyserialized request: missing enclosing parameter atarray serialization.It worked with 1.1 but not with 1.3.I also noticed that in 1.3, the stubs generated are slightly different from the one generated with 1.1...Is there any workaround or solution to this issue?PS.: I also tried the nightly build last fridaywithout more success.> Subject:array serialization in 1.3> From: Erik Wright ! com>> Date: 2006-01-31 20:44:27> Message-ID: 1138740266.27449.59.camel () localhost !localdomain> [Download message RAW] >> Hi,>> I have noticed that array parameters (in or out)seem to be serialized> incorrectly in Axis 1.3. I am attaching a sampleWSDL here, along with> the corresponding input and output. In summary, instead of creating an> element for the array parameter (containing thearray members) it> creates one element for each member, without anyall-enclosing parent.>> Note that we are using WSDL2Java to generate the service implementation> from existing wsdl.>> WSDL snippet (complete wsdl attached):>> > />> />> type="impl:positiveFloat" />> >> Serialized output (simplified slightly - completeoutput attached):>> > > hello > > > good> > > bye > > xsi:type="ns4:positiveFloat">11.7> >> In Axis 1.1 this worked as expected. Is there anyway to get this to> serialize as:>> > soapenc:arrayType="ns1:Foo[1]" >> > hello> > > soapenc:arrayType="ns1:Bar[2]" > > > good> > > bye > > > xsi:type="ns4:positiveFloat">11.7> >> Thanks for your help in advance. >> -Erik>> ["demo.wsdl" (demo.wsdl)]>> > >targetNamespace=" http://demo.radialpoint.com/service"> xmlns="http://schemas.xmlsoap.org/wsdl/"> xmlns:wsdl=" http://schemas.xmlsoap.org/wsdl/">xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"> xmlns:xsd=" http://www.w3.org/2001/XMLSchema">xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"> xmlns:impl=" http://demo.radialpoint.com/service"> xmlns:type="http://demo.radialpoint.com/type">> > > targetNamespace="http://demo.radialpoint.com/type"> xmlns="http://www.w3.org/2001/XMLSchema"> >> > > type="xsd:string"/>> > >> > > type="xsd:string"/> > > >> > > type="xsd:string"/>> > >> > > type="xsd:string"/>> > > >> >targetNamespace=" http://demo.radialpoint.com/service"> xmlns="http://www.w3.org/2001/XMLSchema">> namespace=" http://demo.radialpoint.com/type"/>>> > > > > > type="type:Foo" minOccurs="0"> maxOccurs="unbounded" /> > > > wsdl:arrayType="type:Foo[]" />> > > >> > > > > > type="type:Bar" minOccurs="0"> maxOccurs="unbounded" />> > > wsdl:arrayType="type:Bar[]" />> > > >> > > > > > type="type:Blah" minOccurs="0"> maxOccurs="unbounded" />> > > wsdl:arrayType="type:Blah[]" />> > > >> > > > >> > > > > >>
Re: array serialization in 1.3
Hi all, I seem to run in the same issue as Erik. I have an Axis client that sends incorrectly serialized request: missing enclosing parameter at array serialization. It worked with 1.1 but not with 1.3. I also noticed that in 1.3, the stubs generated are slightly different from the one generated with 1.1... Is there any workaround or solution to this issue? PS.: I also tried the nightly build last friday without more success. > Subject: array serialization in 1.3 > From: Erik Wright > Date: 2006-01-31 20:44:27 > Message-ID: 1138740266.27449.59.camel () localhost ! localdomain > [Download message RAW] > > Hi, > > I have noticed that array parameters (in or out) seem to be serialized > incorrectly in Axis 1.3. I am attaching a sample WSDL here, along with > the corresponding input and output. In summary, instead of creating an > element for the array parameter (containing the array members) it > creates one element for each member, without any all-enclosing parent. > > Note that we are using WSDL2Java to generate the service implementation > from existing wsdl. > > WSDL snippet (complete wsdl attached): > > > > > > > > Serialized output (simplified slightly - complete output attached): > > > > hello > > > good > > > bye > > 11.7 > > > In Axis 1.1 this worked as expected. Is there anyway to get this to > serialize as: > > > > > hello > > > > > good > > > bye > > > 11.7 > > > Thanks for your help in advance. > > -Erik > > ["demo.wsdl" (demo.wsdl)] > > > targetNamespace="http://demo.radialpoint.com/service"; > xmlns="http://schemas.xmlsoap.org/wsdl/"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; > xmlns:impl="http://demo.radialpoint.com/service"; > xmlns:type="http://demo.radialpoint.com/type";> > > targetNamespace="http://demo.radialpoint.com/type"; > xmlns="http://www.w3.org/2001/XMLSchema";> > > > > > > > > > > > > > > > > > > > > > > > > > > > targetNamespace="http://demo.radialpoint.com/service"; > xmlns="http://www.w3.org/2001/XMLSchema";> > http://demo.radialpoint.com/type"/> > > > > > >type="type:Foo" minOccurs="0" > maxOccurs="unbounded" /> > >wsdl:arrayType="type:Foo[]" /> > > > > > > > > >type="type:Bar" minOccurs="0" > maxOccurs="unbounded" /> > >wsdl:arrayType="type:Bar[]" /> > > > > > > > > >type="type:Blah" minOccurs="0" > maxOccurs="unbounded" /> > >wsdl:arrayType="type:Blah[]" /> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >parameterOrder="Boing Blahs"> >name="DemoRequest" /> >name="DemoResponse" /> >name="CustomException" /> > > > >type="impl:DemoService"> > transport="http://schemas.xmlsoap.org/soap/http"; /> > > > > encodingStyle="http://schemas.xmlsoap.org/soap/enco
array serialization in 1.3
Hi, I have noticed that array parameters (in or out) seem to be serialized incorrectly in Axis 1.3. I am attaching a sample WSDL here, along with the corresponding input and output. In summary, instead of creating an element for the array parameter (containing the array members) it creates one element for each member, without any all-enclosing parent. Note that we are using WSDL2Java to generate the service implementation from existing wsdl. WSDL snippet (complete wsdl attached): Serialized output (simplified slightly - complete output attached): hello good bye 11.7 In Axis 1.1 this worked as expected. Is there anyway to get this to serialize as: hello good bye 11.7 Thanks for your help in advance. -Erik http://demo.radialpoint.com/service"; xmlns="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:impl="http://demo.radialpoint.com/service"; xmlns:type="http://demo.radialpoint.com/type";> http://demo.radialpoint.com/type"; xmlns="http://www.w3.org/2001/XMLSchema";> http://demo.radialpoint.com/service"; xmlns="http://www.w3.org/2001/XMLSchema";> http://demo.radialpoint.com/type"/> http://schemas.xmlsoap.org/soap/http"; /> http://schemas.xmlsoap.org/soap/encoding/"; namespace="http://demo.radialpoint.com/service"; use="literal" /> http://schemas.xmlsoap.org/soap/encoding/"; namespace="http://demo.radialpoint.com/service"; use="literal" /> http://schemas.xmlsoap.org/soap/encoding/"; namespace="http://demo.radialpoint.com/service"; use="literal"/> http://localhost:7001/demo-service/services/demo-service/1.0"; /> POST /demo-service/services/demo-service/1.0 HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.4 Host: localhost:7001 Cache-Control: no-cache Pragma: no-cache SOAPAction: "" Content-Length: 499 http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>http://demo.radialpoint.com/service";>boing boingnyuk nyukda da da HTTP/1.1 200 OK Connection: close Date: Tue, 31 Jan 2006 20:25:43 GMT Content-Type: text/xml; charset=utf-8 X-Powered-By: Servlet/2.4 JSP/2.0 http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>http://demo.radialpoint.com/service";>http://demo.radialpoint.com/type";>hellohttp://demo.radialpoint.com/type";>goodhttp://demo.radialpoint.com/type";>byehttp://demo.radialpoint.com/service";>11.7
