Anne
On 3/16/06, Marc Brette
<[EMAIL PROTECTED]> wrote:
Then this may not be the same issue. The binding is
defined as follow:
<binding name="SearchSoapBinding"
type="tns:SearchSoapPort">
<soap11:binding style="document"
transport=" http://schemas.xmlsoap.org/soap/http"/>
<operation name="Search">
<soap11:operation soapAction=""/>
<input>
<soap11:body use="literal"/>
</input>
<output>
<soap11:body use="literal"/>
</output>
</operation>
<operation name="NarrowSearch">
<soap11:operation soapAction=""/>
<input>
<soap11:body use="literal"/>
</input>
<output>
<soap11:body use="literal"/>
</output>
</operation>
</binding>
See below the axis 1.1 request (that works) and the
axis 1.3 request:
1.1: (I cut some part for simplicity sake)
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope
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">
<soapenv:Body>
<Search
xmlns=" http://search.search.services.v1.wsapi.lexisnexis.com">
<binarySecurityToken>[...]</binarySecurityToken>
<sourceInformation>
<ns1:sourceIdList
xmlns:ns1=" http://common.search.services.v1.wsapi.lexisnexis.com">
<ns2:sourceId
xmlns:ns2="http://common.services.v1.wsapi.lexisnexis.com">274668</ns2:sourceId>
</ns1:sourceIdList>
</sourceInformation>
<query>[...]</query>
<projectId>[...]</projectId>
<searchOptions>[...]
</searchOptions>
<retrievalOptions>[...]
</retrievalOptions>
</Search>
</soapenv:Body>
</soapenv:Envelope>
1.3 (look at the difference in the sourceIdList tag)
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope
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">
<soapenv:Body>
<Search
xmlns=" http://search.search.services.v1.wsapi.lexisnexis.com">
<binarySecurityToken>[...]</binarySecurityToken>
<sourceInformation>
<ns1:sourceIdList xsi:type="xsd:integer"
xmlns:ns1="http://common.search.services.v1.wsapi.lexisnexis.com">274668</ns1:sourceIdList>
</sourceInformation>
<query>[...]</query>
<projectId>[...]</projectId>
<searchOptions>[...]</searchOptions>
<retrievalOptions>[...]</retrievalOptions>
</Search>
</soapenv:Body>
</soapenv:Envelope>
--- 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 <element
> type="soapenc:int" nillable="false"/>
> > still maps to Integer (not int)? Or only when
> use="encoded"?
> >
> > > <wsdlsoap:body encodingStyle="
> > http://schemas.xmlsoap.org/soap/encoding/"
> > >
> namespace="http://demo.radialpoint.com/service"
> use="literal" />
> > >
> > > It should say:
> > >
> > > <wsdlsoap:body encodingStyle="
> > 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?
> >
> > <wsdlsoap:body
> 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
