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:> >
>
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:
>
>
>
>
>
>
>
>
>
>
>
Here it is:
Opt
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:[..
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"/>
[...]
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.xml
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 f
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 thecon
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
ng 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.&g
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
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 ele
12 matches
Mail list logo