You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Adnene <ab...@infovista.com> on 2006/09/04 18:03:47 UTC
Re: Axis array serialization problem (Adnene problem)
Hi all,
Did any body have time to have a look at this problem?
I posted my WSDL file a week ago.
I can't find a solution to this problem.
Please let me know if you find something consernig this deserialization
problem.
Thanks,
Adnene
HHDirecto.Net wrote:
>
> Hi, Adnene can you post your wsdl and wsdd files to compare with mine?
>
>
> 2006/8/24, Adnene <ab...@infovista.com>:
>>
>>
>> I don't get a solution yet. But I am trying to anderstand the problem.
>> Why don't you think it is the same problem? Do you know people having the
>> same problem? I am new with Axis. Do you think it is a bug or a missuse
>> of
>> Axis?
>>
>> Thanks,
>> Adnene
>>
>>
>> HHDirecto.Net wrote:
>> >
>> > I think it isnot the same problem, but You found the solution?
>> >
>> > ----- Original Message -----
>> > From: "Adnene" <ab...@infovista.com>
>> > To: <ax...@ws.apache.org>
>> > Sent: Wednesday, August 23, 2006 2:20 PM
>> > Subject: Re: Axis array serialization problem
>> >
>> >
>> >>
>> >> This seems to be like the problem I got with the deserialization of
>> >> ArrayOf_xsd_string type.
>> >> See the message I posted in :
>> >>
>> http://www.nabble.com/deserialization-problem-in-axis-1.4-for-an-array-of-string-tf2146972.html
>> >>
>> http://www.nabble.com/deserialization-problem-in-axis-1.4-for-an-array-of-string-tf2146972.html
>> >>
>> >>
>> >> HHDirecto.Net wrote:
>> >>>
>> >>> Axis web service response is ok (I think) but, .net client don't get
>> >>> "plantas" array it get null (Now It get int array successfull).
>> >>>
>> >>>
>> >>>
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/Axis-array-serialization-problem-tf2139637.html#a5943306
>> >> Sent from the Axis - User forum at Nabble.com.
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >> For additional commands, e-mail: axis-user-help@ws.apache.org
>> >>
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> > For additional commands, e-mail: axis-user-help@ws.apache.org
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Axis-array-serialization-problem-tf2139637.html#a5958931
>> Sent from the Axis - User forum at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Re%3A-Axis-array-serialization-problem-%28Adnene-problem%29-tf2157136.html#a6137973
Sent from the Axis - User forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis array serialization problem (Adnene problem)
Posted by Adnene <ab...@infovista.com>.
Hi all,
It seems that the problem I have with deserialising array of strings is
know bug:
http://issues.apache.org/jira/browse/AXIS-2485
http://issues.apache.org/jira/browse/AXIS-2485
Did someone had a look at this problem? The bug seems not to be planned. Can
anyone help me in getting this bug solved?
Adnene
--
View this message in context: http://www.nabble.com/Re%3A-Axis-array-serialization-problem-%28Adnene-problem%29-tf2157136.html#a6483093
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Socket connection on Client and Server not disconnecting
Posted by robert lazarski <ro...@gmail.com>.
Actually, I meant attach all that to the jira:
http://issues.apache.org/jira/browse/AXIS2-935
Robert
On 9/19/06, robert lazarski <ro...@gmail.com> wrote:
>
> I think its an internal axis2 issue in that the httpclient call needs to
> invoke closeIdleConnections() . I've battled CLOSE_WAIT issues a few times
> and I think I know what's happening. If you attach your source here, and
> attach your netstat output along with how long the CLOSE_WAIT condition
> lasts, I'll try and reproduce the error and then try to fix it.
>
> Robert
>
> On 9/19/06, Brian Bacsu <bb...@csc.com> wrote:
> >
> >
> > Robert
> >
> > Is this an issue with ServiceClient's finalizeInvoke() method not
> > properly cleaning up the connection? Would I experience the same socket
> > resource starvation with Axis2 if I reverted to a simpler implementation
> > using the ServiceClient.sendReceive() method, rather than the
> > OperationClient.execute() method?
> >
> > Thanks,
> >
> > Brian Bacsu
> >
> >
> >
> > *"robert lazarski" <ro...@gmail.com>*
> >
> > 09/19/2006 01:42 PM Please respond to
> > axis-user@ws.apache.org
> >
> > To
> > axis-user@ws.apache.org cc
> >
> > Subject
> > Re: [Axis2] Socket connection on Client and Server not disconnecting
> >
> >
> >
> >
> >
> >
> > This is a known issue:
> >
> > http://issues.apache.org/jira/browse/AXIS2-935
> >
> > There is a patch submitted. If you could attach your test case to it
> > I'll take a look at the patch.
> >
> > Robert
> >
> > On 9/19/06, Brian Bacsu <bb...@csc.com> wrote:
> > >
> > > Hi,
> > >
> > > We have implemented an Axis2 client to call web services exposed
> > through
> > > both .NET and Axis1 running on Microsoft Server 2003. I have
> > encountered an
> > > issue with the Axis2 client with regard to disconnecting the client
> > and
> > > server socket connections. The server-side connection will finally
> > time-out
> > > and drop (It looks like Microsoft Server will hang onto connections
> > for 60
> > > seconds, even after close requested), but the client side connections
> > > continue to collect until the server begins to run out of
> > > resources/connections. The client connections show CLOSE_WAIT status
> > when
> > > viewed with netstat .
> > >
> > > Any suggestions would be appreciated.
> > >
> > > Here is a sample of the client code:
> > >
> > > Options options = new Options();
> > >
> > >
> > > options.setExceptionToBeThrownOnSOAPFault(Boolean.TRUE);
> > >
> > > options.setTo(new EndpointReference(url.toString()));
> > > ServiceClient serviceClient = null;
> > > MessageContext requestContext =
> > > CFWsoapClient.getMessageContext(OM_Msg,this,soapRoot, logger,
> > traceLevel);
> > > requestContext.setSoapAction(action);
> > > try {
> > >
> > > options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
> > > options.setProperty(HTTPConstants.SO_TIMEOUT,1000);
> > > options.setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
> > > Boolean.FALSE);
> > >
> > > options.setProperty(HTTPConstants.CONNECTION_TIMEOUT,
> > > (int)timeout);
> > >
> > > serviceClient = new ServiceClient();
> > > serviceClient.setOptions(options);
> > > OperationClient opClient =
> > > serviceClient.createClient(ServiceClient.ANON_OUT_IN_OP);
> > > opClient.addMessageContext(requestContext);
> > > opClient.execute(true);
> > >
> > > MessageContext resultContext =
> > > opClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
> > >
> > > SOAPEnvelope resEnvelope = resultContext.getEnvelope();
> > > SOAPBody body = resEnvelope.getBody();
> > >
> > > opClient.complete(resultContext);
> > > return body;
> > > }
> > > catch (AxisFault e1) {
> > > e1.printStackTrace();
> > > throw new AxisFault(e1.getMessage());
> > > }
> > > finally {
> > > try {
> > > serviceClient.finalizeInvoke();
> > > } catch (AxisFault axisFault) {
> > > logger.error(axisFault.getMessage() +
> > > axisFault.toString());
> > > } catch (Exception e) {
> > > logger.error(e.getMessage() + e.toString());
> > > }
> > >
> > > }
> > >
> > > Thanks,
> > >
> > > Brian Bacsu
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
> >
>
Re: [Axis2] Socket connection on Client and Server not disconnecting
Posted by robert lazarski <ro...@gmail.com>.
I think its an internal axis2 issue in that the httpclient call needs to
invoke closeIdleConnections() . I've battled CLOSE_WAIT issues a few times
and I think I know what's happening. If you attach your source here, and
attach your netstat output along with how long the CLOSE_WAIT condition
lasts, I'll try and reproduce the error and then try to fix it.
Robert
On 9/19/06, Brian Bacsu <bb...@csc.com> wrote:
>
>
> Robert
>
> Is this an issue with ServiceClient's finalizeInvoke() method not properly
> cleaning up the connection? Would I experience the same socket resource
> starvation with Axis2 if I reverted to a simpler implementation using the
> ServiceClient.sendReceive() method, rather than the
> OperationClient.execute() method?
>
> Thanks,
>
> Brian Bacsu
>
>
>
> *"robert lazarski" <ro...@gmail.com>*
>
> 09/19/2006 01:42 PM Please respond to
> axis-user@ws.apache.org
>
> To
> axis-user@ws.apache.org cc
>
> Subject
> Re: [Axis2] Socket connection on Client and Server not disconnecting
>
>
>
>
>
>
> This is a known issue:
>
> http://issues.apache.org/jira/browse/AXIS2-935
>
> There is a patch submitted. If you could attach your test case to it
> I'll take a look at the patch.
>
> Robert
>
> On 9/19/06, Brian Bacsu <bb...@csc.com> wrote:
> >
> > Hi,
> >
> > We have implemented an Axis2 client to call web services exposed through
> > both .NET and Axis1 running on Microsoft Server 2003. I have encountered
> an
> > issue with the Axis2 client with regard to disconnecting the client and
> > server socket connections. The server-side connection will finally
> time-out
> > and drop (It looks like Microsoft Server will hang onto connections for
> 60
> > seconds, even after close requested), but the client side connections
> > continue to collect until the server begins to run out of
> > resources/connections. The client connections show CLOSE_WAIT status
> when
> > viewed with netstat .
> >
> > Any suggestions would be appreciated.
> >
> > Here is a sample of the client code:
> >
> > Options options = new Options();
> >
> >
> > options.setExceptionToBeThrownOnSOAPFault(Boolean.TRUE);
> >
> > options.setTo(new EndpointReference(url.toString()));
> > ServiceClient serviceClient = null;
> > MessageContext requestContext =
> > CFWsoapClient.getMessageContext(OM_Msg,this,soapRoot, logger,
> traceLevel);
> > requestContext.setSoapAction(action);
> > try {
> >
> > options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
> > options.setProperty(HTTPConstants.SO_TIMEOUT,1000);
> > options.setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
> > Boolean.FALSE);
> >
> > options.setProperty(HTTPConstants.CONNECTION_TIMEOUT,
> > (int)timeout);
> >
> > serviceClient = new ServiceClient();
> > serviceClient.setOptions(options);
> > OperationClient opClient =
> > serviceClient.createClient(ServiceClient.ANON_OUT_IN_OP);
> > opClient.addMessageContext(requestContext);
> > opClient.execute(true);
> >
> > MessageContext resultContext =
> > opClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
> >
> > SOAPEnvelope resEnvelope = resultContext.getEnvelope();
> > SOAPBody body = resEnvelope.getBody();
> >
> > opClient.complete(resultContext);
> > return body;
> > }
> > catch (AxisFault e1) {
> > e1.printStackTrace();
> > throw new AxisFault(e1.getMessage());
> > }
> > finally {
> > try {
> > serviceClient.finalizeInvoke();
> > } catch (AxisFault axisFault) {
> > logger.error(axisFault.getMessage() +
> > axisFault.toString());
> > } catch (Exception e) {
> > logger.error(e.getMessage() + e.toString());
> > }
> >
> > }
> >
> > Thanks,
> >
> > Brian Bacsu
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
Re: [Axis2] Socket connection on Client and Server not disconnecting
Posted by Brian Bacsu <bb...@csc.com>.
Robert
Is this an issue with ServiceClient's finalizeInvoke() method not properly
cleaning up the connection? Would I experience the same socket resource
starvation with Axis2 if I reverted to a simpler implementation using the
ServiceClient.sendReceive() method, rather than the
OperationClient.execute() method?
Thanks,
Brian Bacsu
"robert lazarski" <ro...@gmail.com>
09/19/2006 01:42 PM
Please respond to
axis-user@ws.apache.org
To
axis-user@ws.apache.org
cc
Subject
Re: [Axis2] Socket connection on Client and Server not disconnecting
This is a known issue:
http://issues.apache.org/jira/browse/AXIS2-935
There is a patch submitted. If you could attach your test case to it
I'll take a look at the patch.
Robert
On 9/19/06, Brian Bacsu <bb...@csc.com> wrote:
>
> Hi,
>
> We have implemented an Axis2 client to call web services exposed through
> both .NET and Axis1 running on Microsoft Server 2003. I have encountered
an
> issue with the Axis2 client with regard to disconnecting the client and
> server socket connections. The server-side connection will finally
time-out
> and drop (It looks like Microsoft Server will hang onto connections for
60
> seconds, even after close requested), but the client side connections
> continue to collect until the server begins to run out of
> resources/connections. The client connections show CLOSE_WAIT status
when
> viewed with netstat .
>
> Any suggestions would be appreciated.
>
> Here is a sample of the client code:
>
> Options options = new Options();
>
>
> options.setExceptionToBeThrownOnSOAPFault(Boolean.TRUE);
>
> options.setTo(new EndpointReference(url.toString()));
> ServiceClient serviceClient = null;
> MessageContext requestContext =
> CFWsoapClient.getMessageContext(OM_Msg,this,soapRoot, logger,
traceLevel);
> requestContext.setSoapAction(action);
> try {
>
> options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
> options.setProperty(HTTPConstants.SO_TIMEOUT,1000);
> options.setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
> Boolean.FALSE);
>
> options.setProperty(HTTPConstants.CONNECTION_TIMEOUT,
> (int)timeout);
>
> serviceClient = new ServiceClient();
> serviceClient.setOptions(options);
> OperationClient opClient =
> serviceClient.createClient(ServiceClient.ANON_OUT_IN_OP);
> opClient.addMessageContext(requestContext);
> opClient.execute(true);
>
> MessageContext resultContext =
> opClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
>
> SOAPEnvelope resEnvelope = resultContext.getEnvelope();
> SOAPBody body = resEnvelope.getBody();
>
> opClient.complete(resultContext);
> return body;
> }
> catch (AxisFault e1) {
> e1.printStackTrace();
> throw new AxisFault(e1.getMessage());
> }
> finally {
> try {
> serviceClient.finalizeInvoke();
> } catch (AxisFault axisFault) {
> logger.error(axisFault.getMessage() +
> axisFault.toString());
> } catch (Exception e) {
> logger.error(e.getMessage() + e.toString());
> }
>
> }
>
> Thanks,
>
> Brian Bacsu
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] Socket connection on Client and Server not disconnecting
Posted by robert lazarski <ro...@gmail.com>.
This is a known issue:
http://issues.apache.org/jira/browse/AXIS2-935
There is a patch submitted. If you could attach your test case to it
I'll take a look at the patch.
Robert
On 9/19/06, Brian Bacsu <bb...@csc.com> wrote:
>
> Hi,
>
> We have implemented an Axis2 client to call web services exposed through
> both .NET and Axis1 running on Microsoft Server 2003. I have encountered an
> issue with the Axis2 client with regard to disconnecting the client and
> server socket connections. The server-side connection will finally time-out
> and drop (It looks like Microsoft Server will hang onto connections for 60
> seconds, even after close requested), but the client side connections
> continue to collect until the server begins to run out of
> resources/connections. The client connections show CLOSE_WAIT status when
> viewed with netstat .
>
> Any suggestions would be appreciated.
>
> Here is a sample of the client code:
>
> Options options = new Options();
>
>
> options.setExceptionToBeThrownOnSOAPFault(Boolean.TRUE);
>
> options.setTo(new EndpointReference(url.toString()));
> ServiceClient serviceClient = null;
> MessageContext requestContext =
> CFWsoapClient.getMessageContext(OM_Msg,this,soapRoot, logger, traceLevel);
> requestContext.setSoapAction(action);
> try {
>
> options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
> options.setProperty(HTTPConstants.SO_TIMEOUT,1000);
> options.setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
> Boolean.FALSE);
>
> options.setProperty(HTTPConstants.CONNECTION_TIMEOUT,
> (int)timeout);
>
> serviceClient = new ServiceClient();
> serviceClient.setOptions(options);
> OperationClient opClient =
> serviceClient.createClient(ServiceClient.ANON_OUT_IN_OP);
> opClient.addMessageContext(requestContext);
> opClient.execute(true);
>
> MessageContext resultContext =
> opClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
>
> SOAPEnvelope resEnvelope = resultContext.getEnvelope();
> SOAPBody body = resEnvelope.getBody();
>
> opClient.complete(resultContext);
> return body;
> }
> catch (AxisFault e1) {
> e1.printStackTrace();
> throw new AxisFault(e1.getMessage());
> }
> finally {
> try {
> serviceClient.finalizeInvoke();
> } catch (AxisFault axisFault) {
> logger.error(axisFault.getMessage() +
> axisFault.toString());
> } catch (Exception e) {
> logger.error(e.getMessage() + e.toString());
> }
>
> }
>
> Thanks,
>
> Brian Bacsu
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
[Axis2] Socket connection on Client and Server not disconnecting
Posted by Brian Bacsu <bb...@csc.com>.
Hi,
We have implemented an Axis2 client to call web services exposed through
both .NET and Axis1 running on Microsoft Server 2003. I have encountered
an issue with the Axis2 client with regard to disconnecting the client and
server socket connections. The server-side connection will finally
time-out and drop (It looks like Microsoft Server will hang onto
connections for 60 seconds, even after close requested), but the client
side connections continue to collect until the server begins to run out of
resources/connections. The client connections show CLOSE_WAIT status when
viewed with netstat .
Any suggestions would be appreciated.
Here is a sample of the client code:
Options options = new Options();
options.setExceptionToBeThrownOnSOAPFault(Boolean.TRUE);
options.setTo(new EndpointReference(url.toString()));
ServiceClient serviceClient = null;
MessageContext requestContext =
CFWsoapClient.getMessageContext(OM_Msg,this,soapRoot, logger, traceLevel);
requestContext.setSoapAction(action);
try {
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
options.setProperty(HTTPConstants.SO_TIMEOUT,1000);
options.setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
Boolean.FALSE);
options.setProperty(HTTPConstants.CONNECTION_TIMEOUT,
(int)timeout);
serviceClient = new ServiceClient();
serviceClient.setOptions(options);
OperationClient opClient =
serviceClient.createClient(ServiceClient.ANON_OUT_IN_OP);
opClient.addMessageContext(requestContext);
opClient.execute(true);
MessageContext resultContext =
opClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
SOAPEnvelope resEnvelope = resultContext.getEnvelope();
SOAPBody body = resEnvelope.getBody();
opClient.complete(resultContext);
return body;
}
catch (AxisFault e1) {
e1.printStackTrace();
throw new AxisFault(e1.getMessage());
}
finally {
try {
serviceClient.finalizeInvoke();
} catch (AxisFault axisFault) {
logger.error(axisFault.getMessage() +
axisFault.toString());
} catch (Exception e) {
logger.error(e.getMessage() + e.toString());
}
}
Thanks,
Brian Bacsu
Re: Axis array serialization problem (Adnene problem)
Posted by Adnene <ab...@infovista.com>.
Hi Anne, Hi all,
I found in the Axis - Dev forum a similar problem :
http://www.nabble.com/-jira--Created%3A-%28AXIS-2485%29-Output-Messages-using-soapenc%3AArray-deserialize-to-arrays-with-null-elements-tf1699379.html#a4611675
http://www.nabble.com/-jira--Created%3A-%28AXIS-2485%29-Output-Messages-using-soapenc%3AArray-deserialize-to-arrays-with-null-elements-tf1699379.html#a4611675
Can you confirm that this is the same problem as mine? If so I suppose
that this is bug. In this case does anyone know if this bug is referenced
and how could we fix it?
Cheers,
Adnene
Adnene wrote:
>
> I already did this change before, Anne. And after regenrating the stubs
> (with xsd:string[]) I have the same behavior. Nothing seems to have
> changed.
>
> For more information, when I perform a diff on the generated files in both
> cases, the only difference I noticed concerns line 94 of
> CDRonDemandSoapBindingStub.java file:
>
> qName = new
> javax.xml.namespace.QName("http://www.w3.org/2001/XMLSchema", "string");
>
> for xsd:string[] instead of
>
> qName = new
> javax.xml.namespace.QName("http://schemas.xmlsoap.org/soap/encoding/",
> "string");
>
> for soapenc:string[].
>
>
> And both cases show the same problem.
>
> Adnene
>
>
> Anne Thomas Manes wrote:
>>
>> Ah ... I see.
>>
>> The problem is with the service. According to the WSDL, it says that
>> it will send you elements of type soapenc:string, but it's actually
>> sending you elements of type xsd:string. You can edit the WSDL
>> document and change the definitions to xsd:string, regen your client
>> stubs, and then it should work.
>>
>> Anne
>>
>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Re%3A-Axis-array-serialization-problem-%28Adnene-problem%29-tf2157136.html#a6390564
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis array serialization problem (Adnene problem)
Posted by Adnene <ab...@infovista.com>.
I already did this change before, Anne. And after regenrating the stubs (with
xsd:string[]) I have the same behavior. Nothing seems to have changed.
For more information, when I perform a diff on the generated files in both
cases, the only difference I noticed concerns line 94 of
CDRonDemandSoapBindingStub.java file:
qName = new
javax.xml.namespace.QName("http://www.w3.org/2001/XMLSchema", "string");
for xsd:string[] instead of
qName = new
javax.xml.namespace.QName("http://schemas.xmlsoap.org/soap/encoding/",
"string");
for soapenc:string[].
And both cases show the same problem.
Adnene
Anne Thomas Manes wrote:
>
> Ah ... I see.
>
> The problem is with the service. According to the WSDL, it says that
> it will send you elements of type soapenc:string, but it's actually
> sending you elements of type xsd:string. You can edit the WSDL
> document and change the definitions to xsd:string, regen your client
> stubs, and then it should work.
>
> Anne
>
>
>
>
--
View this message in context: http://www.nabble.com/Re%3A-Axis-array-serialization-problem-%28Adnene-problem%29-tf2157136.html#a6170656
Sent from the Axis - User forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis array serialization problem (Adnene problem)
Posted by Anne Thomas Manes <at...@gmail.com>.
Ah ... I see.
The problem is with the service. According to the WSDL, it says that
it will send you elements of type soapenc:string, but it's actually
sending you elements of type xsd:string. You can edit the WSDL
document and change the definitions to xsd:string, regen your client
stubs, and then it should work.
Anne
On 9/6/06, Adnene <ab...@infovista.com> wrote:
>
> Thanks Anne for your explaination.
>
> I just want to precise that I am not writing the service agebt part of
> the webservice but
> only the client part by generating the client java stubs from the WSDL
> provided by the service
> using the wsdl2java AXIS utility.
>
> Do I still have to get a WSDD file? And how and when shoud I use this WSDD
> file to generate my stubs?
>
> Thanks,
> Adnene
>
>
> Anne Thomas Manes wrote:
> >
> > WSDD = web service deployment descriptor
> > It tells Axis how to map incoming SOAP requests to your service agent.
> > If you haven't encountered a WSDD yet, I gather that you are using the
> > .jws deployment method. You should only use the .jws method when using
> > simple types. I suggest you progress to the next level and start
> > deploying your service with a WSDD.
> >
> > Anne
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Re%3A-Axis-array-serialization-problem-%28Adnene-problem%29-tf2157136.html#a6170032
> Sent from the Axis - User forum at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis array serialization problem (Adnene problem)
Posted by Adnene <ab...@infovista.com>.
Thanks Anne for your explaination.
I just want to precise that I am not writing the service agebt part of
the webservice but
only the client part by generating the client java stubs from the WSDL
provided by the service
using the wsdl2java AXIS utility.
Do I still have to get a WSDD file? And how and when shoud I use this WSDD
file to generate my stubs?
Thanks,
Adnene
Anne Thomas Manes wrote:
>
> WSDD = web service deployment descriptor
> It tells Axis how to map incoming SOAP requests to your service agent.
> If you haven't encountered a WSDD yet, I gather that you are using the
> .jws deployment method. You should only use the .jws method when using
> simple types. I suggest you progress to the next level and start
> deploying your service with a WSDD.
>
> Anne
>
>
--
View this message in context: http://www.nabble.com/Re%3A-Axis-array-serialization-problem-%28Adnene-problem%29-tf2157136.html#a6170032
Sent from the Axis - User forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis array serialization problem (Adnene problem)
Posted by Anne Thomas Manes <at...@gmail.com>.
WSDD = web service deployment descriptor
It tells Axis how to map incoming SOAP requests to your service agent.
If you haven't encountered a WSDD yet, I gather that you are using the
.jws deployment method. You should only use the .jws method when using
simple types. I suggest you progress to the next level and start
deploying your service with a WSDD.
Anne
On 9/6/06, Adnene <ab...@infovista.com> wrote:
>
> Hi Anne,
>
> I already tried with xsd:string instead of soapenc:string but I got the
> same behavior.
>
> Concerning the WSDD, I don't know where I find such file. I do not use
> explicitely a WSDD.
> I am a little new with AXIS and SOAP. Can you explain me what is it about
> and is the WSDD is for?
>
> Thanks
> Adnene
>
>
> Anne Thomas Manes wrote:
> >
> > Your schema indicates that the inner type in the array should be
> > soapenc:string, but the message actually returns xsd:string.
> >
> > Do you have a parameter set in the WSDD that specifies the .NET SOAP
> > encoding fix is true? If so, try setting it to false. (or edit the
> > WSDL to specify that the inner type is xsd:string)
> >
> > Anne
> >
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Re%3A-Axis-array-serialization-problem-%28Adnene-problem%29-tf2157136.html#a6166322
> Sent from the Axis - User forum at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis array serialization problem (Adnene problem)
Posted by Adnene <ab...@infovista.com>.
Hi Anne,
I already tried with xsd:string instead of soapenc:string but I got the
same behavior.
Concerning the WSDD, I don't know where I find such file. I do not use
explicitely a WSDD.
I am a little new with AXIS and SOAP. Can you explain me what is it about
and is the WSDD is for?
Thanks
Adnene
Anne Thomas Manes wrote:
>
> Your schema indicates that the inner type in the array should be
> soapenc:string, but the message actually returns xsd:string.
>
> Do you have a parameter set in the WSDD that specifies the .NET SOAP
> encoding fix is true? If so, try setting it to false. (or edit the
> WSDL to specify that the inner type is xsd:string)
>
> Anne
>
>
>
>
--
View this message in context: http://www.nabble.com/Re%3A-Axis-array-serialization-problem-%28Adnene-problem%29-tf2157136.html#a6166322
Sent from the Axis - User forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis array serialization problem (Adnene problem)
Posted by Anne Thomas Manes <at...@gmail.com>.
Your schema indicates that the inner type in the array should be
soapenc:string, but the message actually returns xsd:string.
Do you have a parameter set in the WSDD that specifies the .NET SOAP
encoding fix is true? If so, try setting it to false. (or edit the
WSDL to specify that the inner type is xsd:string)
Anne
On 9/5/06, Adnene <ab...@infovista.com> wrote:
>
> I am writing a client that access a webservise whose WSDL file is provided in
> the attachments.
> The binding stubs has been generated using WSDL2Java of AXIS 1.4.
> The webservice provides a method 'get_file_list' that returns a list of file
> names as string array. This method returns a get_file_listReturn object of
> type ArrayOf_xsd_string containing a list of strings.
>
> An example of a responce to the call of 'get_file_list' is as follows:
>
> <?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>
> <ns1:get_file_listResponse
> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> xmlns:ns1="http://schemas.cisco.com/ast/soap/">
> <get_file_listReturn soapenc:arrayType="ns1:ArrayOf_xsd_string[22]"
> xsi:type="soapenc:Array"
> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
> <item
> xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221000_3577</item>
> <item
> xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221000_3577</item>
> <item
> xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221010_3578</item>
> <item
> xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221010_3578</item>
> <item
> xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221015_3579</item>
> <item
> xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221015_3579</item>
> <item
> xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221020_3580</item>
> <item
> xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221020_3580</item>
> <item
> xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221025_3581</item>
> <item
> xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221025_3581</item>
> <item
> xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221030_3582</item>
> <item
> xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221030_3582</item>
> <item
> xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221040_3583</item>
> <item
> xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221040_3583</item>
> <item
> xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221045_3584</item>
> <item
> xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221045_3584</item>
> <item
> xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221050_3585</item>
> <item
> xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221050_3585</item>
> <item
> xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221055_3586</item>
> <item
> xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221055_3586</item>
> <item
> xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221100_3587</item>
> <item
> xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221100_3587</item>
> </get_file_listReturn>
> </ns1:get_file_listResponse>
> </soapenv:Body>
> </soapenv:Envelope>
>
>
> The problem here is that AXIS does not seem to deserialize correctly the
> result received in the SOAP answer. The AXIS stub returns an array of null
> strings instead of the correct answer. Note that even if the returned array
> conatins only NULL elements, its size is correct. For example if the
> expected answer is an array of 22 file names, the returned string array
> contains 22 NULLs.
>
> The problem seems to happen during the call of the
> ArrayUtil.convertArrayToObject(arg, destClass) java method.
> For example, in the cotext of the example described above, the arg parameter
> value of the ArrayUtil.convertArrayToObject java method is :
> [[cdr_StandAloneCluster_01_200608221000_3577],
> [cmr_StandAloneCluster_01_200608221000_3577], ..]
> where the returned value is :
> [null, null, ...].
> The correct return value if this java method should be :
> [cdr_StandAloneCluster_01_200608221000_3577,
> cmr_StandAloneCluster_01_200608221000_3577, ..]
>
>
> I hope the description of my problem is clear enough and thank you for
> helping me solving this problem.
> Yours,
>
> Adnene BEN ABDALLAH
>
>
> Anne Thomas Manes wrote:
> >
> > Please repost the description of your problem with the WSDL file.
> >
> > Anne
> >
> > On 9/4/06, Adnene <ab...@infovista.com> wrote:
> >>
> >> Hi all,
> >>
> >> Did any body have time to have a look at this problem?
> >> I posted my WSDL file a week ago.
> >>
> >> I can't find a solution to this problem.
> >> Please let me know if you find something consernig this deserialization
> >> problem.
> >>
> >> Thanks,
> >> Adnene
> >>
> >>
> >> HHDirecto.Net wrote:
> >> >
> >> > Hi, Adnene can you post your wsdl and wsdd files to compare with mine?
> >> >
> >> >
> >> > 2006/8/24, Adnene <ab...@infovista.com>:
> >> >>
> >> >>
> >> >> I don't get a solution yet. But I am trying to anderstand the problem.
> >> >> Why don't you think it is the same problem? Do you know people having
> >> the
> >> >> same problem? I am new with Axis. Do you think it is a bug or a
> >> missuse
> >> >> of
> >> >> Axis?
> >> >>
> >> >> Thanks,
> >> >> Adnene
> >> >>
> >> >>
> >> >> HHDirecto.Net wrote:
> >> >> >
> >> >> > I think it isnot the same problem, but You found the solution?
> >> >> >
> >> >> > ----- Original Message -----
> >> >> > From: "Adnene" <ab...@infovista.com>
> >> >> > To: <ax...@ws.apache.org>
> >> >> > Sent: Wednesday, August 23, 2006 2:20 PM
> >> >> > Subject: Re: Axis array serialization problem
> >> >> >
> >> >> >
> >> >> >>
> >> >> >> This seems to be like the problem I got with the deserialization of
> >> >> >> ArrayOf_xsd_string type.
> >> >> >> See the message I posted in :
> >> >> >>
> >> >>
> >> http://www.nabble.com/deserialization-problem-in-axis-1.4-for-an-array-of-string-tf2146972.html
> >> >> >>
> >> >>
> >> http://www.nabble.com/deserialization-problem-in-axis-1.4-for-an-array-of-string-tf2146972.html
> >> >> >>
> >> >> >>
> >> >> >> HHDirecto.Net wrote:
> >> >> >>>
> >> >> >>> Axis web service response is ok (I think) but, .net client don't
> >> get
> >> >> >>> "plantas" array it get null (Now It get int array successfull).
> >> >> >>>
> >> >> >>>
> >> >> >>>
> >> >> >>
> >> >> >> --
> >> >> >> View this message in context:
> >> >> >>
> >> >>
> >> http://www.nabble.com/Axis-array-serialization-problem-tf2139637.html#a5943306
> >> >> >> Sent from the Axis - User forum at Nabble.com.
> >> >> >>
> >> >> >>
> >> >> >>
> >> ---------------------------------------------------------------------
> >> >> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> >> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> ---------------------------------------------------------------------
> >> >> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> >> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >> --
> >> >> View this message in context:
> >> >>
> >> http://www.nabble.com/Axis-array-serialization-problem-tf2139637.html#a5958931
> >> >> Sent from the Axis - User forum at Nabble.com.
> >> >>
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >> >>
> >> >>
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Re%3A-Axis-array-serialization-problem-%28Adnene-problem%29-tf2157136.html#a6137973
> >> Sent from the Axis - User forum at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
> >
> http://www.nabble.com/user-files/235744/CDRonDemand.wsdl CDRonDemand.wsdl
> --
> View this message in context: http://www.nabble.com/Re%3A-Axis-array-serialization-problem-%28Adnene-problem%29-tf2157136.html#a6152234
> Sent from the Axis - User forum at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis array serialization problem (Adnene problem)
Posted by Adnene <ab...@infovista.com>.
I am writing a client that access a webservise whose WSDL file is provided in
the attachments.
The binding stubs has been generated using WSDL2Java of AXIS 1.4.
The webservice provides a method 'get_file_list' that returns a list of file
names as string array. This method returns a get_file_listReturn object of
type ArrayOf_xsd_string containing a list of strings.
An example of a responce to the call of 'get_file_list' is as follows:
<?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>
<ns1:get_file_listResponse
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="http://schemas.cisco.com/ast/soap/">
<get_file_listReturn soapenc:arrayType="ns1:ArrayOf_xsd_string[22]"
xsi:type="soapenc:Array"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
<item
xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221000_3577</item>
<item
xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221000_3577</item>
<item
xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221010_3578</item>
<item
xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221010_3578</item>
<item
xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221015_3579</item>
<item
xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221015_3579</item>
<item
xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221020_3580</item>
<item
xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221020_3580</item>
<item
xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221025_3581</item>
<item
xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221025_3581</item>
<item
xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221030_3582</item>
<item
xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221030_3582</item>
<item
xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221040_3583</item>
<item
xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221040_3583</item>
<item
xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221045_3584</item>
<item
xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221045_3584</item>
<item
xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221050_3585</item>
<item
xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221050_3585</item>
<item
xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221055_3586</item>
<item
xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221055_3586</item>
<item
xsi:type="xsd:string">cdr_StandAloneCluster_01_200608221100_3587</item>
<item
xsi:type="xsd:string">cmr_StandAloneCluster_01_200608221100_3587</item>
</get_file_listReturn>
</ns1:get_file_listResponse>
</soapenv:Body>
</soapenv:Envelope>
The problem here is that AXIS does not seem to deserialize correctly the
result received in the SOAP answer. The AXIS stub returns an array of null
strings instead of the correct answer. Note that even if the returned array
conatins only NULL elements, its size is correct. For example if the
expected answer is an array of 22 file names, the returned string array
contains 22 NULLs.
The problem seems to happen during the call of the
ArrayUtil.convertArrayToObject(arg, destClass) java method.
For example, in the cotext of the example described above, the arg parameter
value of the ArrayUtil.convertArrayToObject java method is :
[[cdr_StandAloneCluster_01_200608221000_3577],
[cmr_StandAloneCluster_01_200608221000_3577], ..]
where the returned value is :
[null, null, ...].
The correct return value if this java method should be :
[cdr_StandAloneCluster_01_200608221000_3577,
cmr_StandAloneCluster_01_200608221000_3577, ..]
I hope the description of my problem is clear enough and thank you for
helping me solving this problem.
Yours,
Adnene BEN ABDALLAH
Anne Thomas Manes wrote:
>
> Please repost the description of your problem with the WSDL file.
>
> Anne
>
> On 9/4/06, Adnene <ab...@infovista.com> wrote:
>>
>> Hi all,
>>
>> Did any body have time to have a look at this problem?
>> I posted my WSDL file a week ago.
>>
>> I can't find a solution to this problem.
>> Please let me know if you find something consernig this deserialization
>> problem.
>>
>> Thanks,
>> Adnene
>>
>>
>> HHDirecto.Net wrote:
>> >
>> > Hi, Adnene can you post your wsdl and wsdd files to compare with mine?
>> >
>> >
>> > 2006/8/24, Adnene <ab...@infovista.com>:
>> >>
>> >>
>> >> I don't get a solution yet. But I am trying to anderstand the problem.
>> >> Why don't you think it is the same problem? Do you know people having
>> the
>> >> same problem? I am new with Axis. Do you think it is a bug or a
>> missuse
>> >> of
>> >> Axis?
>> >>
>> >> Thanks,
>> >> Adnene
>> >>
>> >>
>> >> HHDirecto.Net wrote:
>> >> >
>> >> > I think it isnot the same problem, but You found the solution?
>> >> >
>> >> > ----- Original Message -----
>> >> > From: "Adnene" <ab...@infovista.com>
>> >> > To: <ax...@ws.apache.org>
>> >> > Sent: Wednesday, August 23, 2006 2:20 PM
>> >> > Subject: Re: Axis array serialization problem
>> >> >
>> >> >
>> >> >>
>> >> >> This seems to be like the problem I got with the deserialization of
>> >> >> ArrayOf_xsd_string type.
>> >> >> See the message I posted in :
>> >> >>
>> >>
>> http://www.nabble.com/deserialization-problem-in-axis-1.4-for-an-array-of-string-tf2146972.html
>> >> >>
>> >>
>> http://www.nabble.com/deserialization-problem-in-axis-1.4-for-an-array-of-string-tf2146972.html
>> >> >>
>> >> >>
>> >> >> HHDirecto.Net wrote:
>> >> >>>
>> >> >>> Axis web service response is ok (I think) but, .net client don't
>> get
>> >> >>> "plantas" array it get null (Now It get int array successfull).
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >>
>> http://www.nabble.com/Axis-array-serialization-problem-tf2139637.html#a5943306
>> >> >> Sent from the Axis - User forum at Nabble.com.
>> >> >>
>> >> >>
>> >> >>
>> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >> >> For additional commands, e-mail: axis-user-help@ws.apache.org
>> >> >>
>> >> >
>> >> >
>> >> >
>> ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >> > For additional commands, e-mail: axis-user-help@ws.apache.org
>> >> >
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/Axis-array-serialization-problem-tf2139637.html#a5958931
>> >> Sent from the Axis - User forum at Nabble.com.
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> >> For additional commands, e-mail: axis-user-help@ws.apache.org
>> >>
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Re%3A-Axis-array-serialization-problem-%28Adnene-problem%29-tf2157136.html#a6137973
>> Sent from the Axis - User forum at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
http://www.nabble.com/user-files/235744/CDRonDemand.wsdl CDRonDemand.wsdl
--
View this message in context: http://www.nabble.com/Re%3A-Axis-array-serialization-problem-%28Adnene-problem%29-tf2157136.html#a6152234
Sent from the Axis - User forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis array serialization problem (Adnene problem)
Posted by Anne Thomas Manes <at...@gmail.com>.
Please repost the description of your problem with the WSDL file.
Anne
On 9/4/06, Adnene <ab...@infovista.com> wrote:
>
> Hi all,
>
> Did any body have time to have a look at this problem?
> I posted my WSDL file a week ago.
>
> I can't find a solution to this problem.
> Please let me know if you find something consernig this deserialization
> problem.
>
> Thanks,
> Adnene
>
>
> HHDirecto.Net wrote:
> >
> > Hi, Adnene can you post your wsdl and wsdd files to compare with mine?
> >
> >
> > 2006/8/24, Adnene <ab...@infovista.com>:
> >>
> >>
> >> I don't get a solution yet. But I am trying to anderstand the problem.
> >> Why don't you think it is the same problem? Do you know people having the
> >> same problem? I am new with Axis. Do you think it is a bug or a missuse
> >> of
> >> Axis?
> >>
> >> Thanks,
> >> Adnene
> >>
> >>
> >> HHDirecto.Net wrote:
> >> >
> >> > I think it isnot the same problem, but You found the solution?
> >> >
> >> > ----- Original Message -----
> >> > From: "Adnene" <ab...@infovista.com>
> >> > To: <ax...@ws.apache.org>
> >> > Sent: Wednesday, August 23, 2006 2:20 PM
> >> > Subject: Re: Axis array serialization problem
> >> >
> >> >
> >> >>
> >> >> This seems to be like the problem I got with the deserialization of
> >> >> ArrayOf_xsd_string type.
> >> >> See the message I posted in :
> >> >>
> >> http://www.nabble.com/deserialization-problem-in-axis-1.4-for-an-array-of-string-tf2146972.html
> >> >>
> >> http://www.nabble.com/deserialization-problem-in-axis-1.4-for-an-array-of-string-tf2146972.html
> >> >>
> >> >>
> >> >> HHDirecto.Net wrote:
> >> >>>
> >> >>> Axis web service response is ok (I think) but, .net client don't get
> >> >>> "plantas" array it get null (Now It get int array successfull).
> >> >>>
> >> >>>
> >> >>>
> >> >>
> >> >> --
> >> >> View this message in context:
> >> >>
> >> http://www.nabble.com/Axis-array-serialization-problem-tf2139637.html#a5943306
> >> >> Sent from the Axis - User forum at Nabble.com.
> >> >>
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >> >>
> >> >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >> >
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Axis-array-serialization-problem-tf2139637.html#a5958931
> >> Sent from the Axis - User forum at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>
> >>
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Re%3A-Axis-array-serialization-problem-%28Adnene-problem%29-tf2157136.html#a6137973
> Sent from the Axis - User forum at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org