You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-user@axis.apache.org by "Robert J. Blanchard" <bo...@access4less.net> on 2004/12/01 14:57:14 UTC
Re: Problem Deserializing a complex type
Christian,
I think this is likely covered by the following:
http://nagoya.apache.org/jira/browse/AXISCPP-136
I, as well as some others, have experienced this problem, too. I know that
it was slated for fixing for the 1.4 Alpha version, but I don't think it
made the cut, and I, for one, haven't been bold enough to dig around and try
and fix it on my own.
I think that Samisa has a good grasp of what needs to be done based on her
comments in JIRA. Hopefully this can be addressed in 1.4 Beta.
Rob
----- Original Message -----
From: "BARBELON C Ext ROSI/DPS" <cb...@francetelecom.com>
To: <ax...@ws.apache.org>
Sent: Monday, November 29, 2004 5:08 AM
Subject: Problem Deserializing a complex type
Hi all,
I'm a newcomer in Axis WebServices solutions and face some serious
interoperability issues between Axis C++ and Axis Java.
I've implemented a server-side WebService using Axis C++ (1.3) on a Linux
platform.
My targeted client is Axis java (1.2) but i first test the WS behavior with
an Axis C++ client.
Problem:
1. Client C++ works fine. Java client does not.
#1: I set the "._setProperty(org.apache.axis.AxisEngine.PROP_DOMULTIREFS,
Boolean.FALSE);" to get rid off 'href/multiref" issues.
#2: I had a look on TCPMonitor and check the HTTP response messages. They
are quite similar for both Axis Java and C++ clients(* see @ the end of the
post).
#3: Java exception is:
Exception in thread "main" AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXException: Invalid element in
localhost.axis.ws_login_view.Ws_LOGIN_VIEW_out - ArrayOfGTCA_serviceArray
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException:
Invalid element in localhost.axis.ws_login_view.Ws_LOGIN_VIEW_out -
ArrayOfGTCA_serviceArray
at
org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.
java:227)
at
org.apache.axis.encoding.DeserializationContextImpl.startElement(Deserializa
tionContextImpl.java:1001)
at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:159)
at
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:
1050)
at
org.apache.axis.message.RPCElement.deserialize(RPCElement.java:196)
at org.apache.axis.message.RPCElement.getParams(RPCElement.java:310)
at org.apache.axis.client.Call.invoke(Call.java:2381)
at org.apache.axis.client.Call.invoke(Call.java:2280)
at org.apache.axis.client.Call.invoke(Call.java:1741)
at
localhost.axis.ws_login_view.Ws_login_viewBindingStub.processGTCQuery(Ws_log
in_viewBindingStub.java:184)
at Testws_login_view.main(Testws_login_view.java:25)
Is there someone here who already faced this kind of problem ?
Thanks for helping hands,
Christian
(*) HTTP response is:
HTTP/1.1 200 OK
Date: Mon, 29 Nov 2004 08:51:27 GMT
Server: Apache/2.0.48 (Unix)
Content-Length: 5168
Connection: close
Content-Type: text/xml
<?xml version='1.0' encoding='utf-8' ?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<ns1:processGTCQueryResponse
xmlns:ns1="http://localhost/axis/ws_login_view">
<ws_LOGIN_VIEW_out xsi:type="ns1:ws_LOGIN_VIEW_out"
xmlns:ns1="http://localhost/axis/ws_login_view">
<ws_status xsi:type="ns1:ws_status"
xmlns:ns1="http://localhost/axis/ws_login_view">
<code xsi:type="xsd:string">0</code>
<msg xsi:type="xsd:string">No error</msg>
</ws_status>
<bundle_access xsi:type="xsd:string">0</bundle_access>
<DB_login xsi:type="ns1:DB_login"
xmlns:ns1="http://localhost/axis/ws_login_view">
<login_id
xsi:type="xsd:string">0X000000250000000185</login_id>
<login xsi:type="xsd:string">test/abcdefg</login>
<passwd xsi:type="xsd:string">XXXXXXXX</passwd>
<passwd_2 xsi:type="xsd:string">YYYYYYYYY</passwd_2>
<passwd_2_end_date
xsi:type="xsd:string">16-SEP-2003</passwd_2_end_date>
<nspace xsi:type="xsd:string">1</nspace>
<account_id
xsi:type="xsd:string">0X000000250000000085</account_id>
</DB_login>
<DB_account xsi:type="ns1:DB_account"
xmlns:ns1="http://localhost/axis/ws_login_view">
<account_id
xsi:type="xsd:string">0X000000250000000085</account_id>
<status xsi:type="xsd:string">1</status>
<begin_date xsi:type="xsd:string">17-SEP-2000</begin_date>
<end_date xsi:type="xsd:string">31-DEC-2030</end_date>
<unavailable_date
xsi:type="xsd:string">NULL</unavailable_date>
<account_poid xsi:type="xsd:string">0 0.0.0.1 / account
000001</account_poid>
<CLID_requested xsi:type="xsd:string">0</CLID_requested>
</DB_account>
<ArrayOfDB_serviceArray
xmlns:enc="http://www.w3.org/2001/06/soap-encoding"
xmlns:ns1="http://localhost/axis/ws_login_view"
enc:arrayType="ns1:ArrayOfDB_service[3]">
<DB_service>
<service_id
xsi:type="xsd:string">0x00000002500000285</service_id>
<service_name xsi:type="xsd:string">MAIN</service_name>
<begin_date
xsi:type="xsd:string">16-SEP-1996</begin_date>
<end_date xsi:type="xsd:string">31-DEC-2030</end_date>
<unavailable_date
xsi:type="xsd:string">NULL</unavailable_date>
<creation_date
xsi:type="xsd:string">16-DEC-1996</creation_date>
<account_id
xsi:type="xsd:string">0X000000250000000085</account_id>
<login_id
xsi:type="xsd:string">0X000000250000000185</login_id>
</DB_service>
<DB_service>
<service_id
xsi:type="xsd:string">0x00000002500000286</service_id>
<service_name xsi:type="xsd:string">MAIN</service_name>
<begin_date
xsi:type="xsd:string">16-SEP-1996</begin_date>
<end_date xsi:type="xsd:string">31-DEC-2030</end_date>
<unavailable_date
xsi:type="xsd:string">NULL</unavailable_date>
<creation_date
xsi:type="xsd:string">16-DEC-1996</creation_date>
<account_id
xsi:type="xsd:string">0X000000250000000085</account_id>
<login_id
xsi:type="xsd:string">0X000000250000000185</login_id>
</DB_service>
<DB_service>
<service_id
xsi:type="xsd:string">0x00000002500000287</service_id>
<service_name xsi:type="xsd:string">MAIN</service_name>
<begin_date
xsi:type="xsd:string">16-SEP-1996</begin_date>
<end_date xsi:type="xsd:string">31-DEC-2030</end_date>
<unavailable_date
xsi:type="xsd:string">NULL</unavailable_date>
<creation_date
xsi:type="xsd:string">16-DEC-1996</creation_date>
<end_date xsi:type="xsd:string">31-DEC-2030</end_date>
<unavailable_date
xsi:type="xsd:string">NULL</unavailable_date>
<creation_date
xsi:type="xsd:string">16-DEC-1996</creation_date>
<account_id
xsi:type="xsd:string">0X000000250000000085</account_id>
<login_id
xsi:type="xsd:string">0X000000250000000185</login_id>
</DB_service>
</ArrayOfDB_serviceArray>
</ws_LOGIN_VIEW_out>
</ns1:processGTCQueryResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Re: Problem Deserializing a complex type
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
I haven not been looking into this Jira issue as I was busy with some other features.
May be I can have a look after 1.4 alpha is done.
However, looking at the timeline, it would be tough to do this before 1.4 beta. May be for 1.5
alpha.
BTW:
> I think that Samisa has a good grasp of what needs to be done based on her
> comments in JIRA.
Should be corrected as "based on *his* comments" ;)
Thanks,
Samisa...
--- "Robert J. Blanchard" <bo...@access4less.net> wrote:
> Christian,
>
> I think this is likely covered by the following:
>
> http://nagoya.apache.org/jira/browse/AXISCPP-136
>
> I, as well as some others, have experienced this problem, too. I know that
> it was slated for fixing for the 1.4 Alpha version, but I don't think it
> made the cut, and I, for one, haven't been bold enough to dig around and try
> and fix it on my own.
>
> I think that Samisa has a good grasp of what needs to be done based on her
> comments in JIRA. Hopefully this can be addressed in 1.4 Beta.
>
>
> Rob
>
> ----- Original Message -----
> From: "BARBELON C Ext ROSI/DPS" <cb...@francetelecom.com>
> To: <ax...@ws.apache.org>
> Sent: Monday, November 29, 2004 5:08 AM
> Subject: Problem Deserializing a complex type
>
>
> Hi all,
>
> I'm a newcomer in Axis WebServices solutions and face some serious
> interoperability issues between Axis C++ and Axis Java.
>
> I've implemented a server-side WebService using Axis C++ (1.3) on a Linux
> platform.
> My targeted client is Axis java (1.2) but i first test the WS behavior with
> an Axis C++ client.
>
> Problem:
> 1. Client C++ works fine. Java client does not.
>
> #1: I set the "._setProperty(org.apache.axis.AxisEngine.PROP_DOMULTIREFS,
> Boolean.FALSE);" to get rid off 'href/multiref" issues.
>
> #2: I had a look on TCPMonitor and check the HTTP response messages. They
> are quite similar for both Axis Java and C++ clients(* see @ the end of the
> post).
>
> #3: Java exception is:
>
> Exception in thread "main" AxisFault
> faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> faultSubcode:
> faultString: org.xml.sax.SAXException: Invalid element in
> localhost.axis.ws_login_view.Ws_LOGIN_VIEW_out - ArrayOfGTCA_serviceArray
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException:
> Invalid element in localhost.axis.ws_login_view.Ws_LOGIN_VIEW_out -
> ArrayOfGTCA_serviceArray
> at
> org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.
> java:227)
> at
> org.apache.axis.encoding.DeserializationContextImpl.startElement(Deserializa
> tionContextImpl.java:1001)
> at
> org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:159)
> at
> org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:
> 1050)
> at
> org.apache.axis.message.RPCElement.deserialize(RPCElement.java:196)
> at org.apache.axis.message.RPCElement.getParams(RPCElement.java:310)
> at org.apache.axis.client.Call.invoke(Call.java:2381)
> at org.apache.axis.client.Call.invoke(Call.java:2280)
> at org.apache.axis.client.Call.invoke(Call.java:1741)
> at
> localhost.axis.ws_login_view.Ws_login_viewBindingStub.processGTCQuery(Ws_log
> in_viewBindingStub.java:184)
> at Testws_login_view.main(Testws_login_view.java:25)
>
>
> Is there someone here who already faced this kind of problem ?
>
> Thanks for helping hands,
>
>
> Christian
>
>
>
> (*) HTTP response is:
>
> HTTP/1.1 200 OK
> Date: Mon, 29 Nov 2004 08:51:27 GMT
> Server: Apache/2.0.48 (Unix)
> Content-Length: 5168
> Connection: close
> Content-Type: text/xml
>
> <?xml version='1.0' encoding='utf-8' ?>
> <SOAP-ENV:Envelope
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> <SOAP-ENV:Body>
> <ns1:processGTCQueryResponse
> xmlns:ns1="http://localhost/axis/ws_login_view">
> <ws_LOGIN_VIEW_out xsi:type="ns1:ws_LOGIN_VIEW_out"
> xmlns:ns1="http://localhost/axis/ws_login_view">
> <ws_status xsi:type="ns1:ws_status"
> xmlns:ns1="http://localhost/axis/ws_login_view">
> <code xsi:type="xsd:string">0</code>
> <msg xsi:type="xsd:string">No error</msg>
> </ws_status>
> <bundle_access xsi:type="xsd:string">0</bundle_access>
> <DB_login xsi:type="ns1:DB_login"
> xmlns:ns1="http://localhost/axis/ws_login_view">
> <login_id
> xsi:type="xsd:string">0X000000250000000185</login_id>
> <login xsi:type="xsd:string">test/abcdefg</login>
> <passwd xsi:type="xsd:string">XXXXXXXX</passwd>
> <passwd_2 xsi:type="xsd:string">YYYYYYYYY</passwd_2>
> <passwd_2_end_date
> xsi:type="xsd:string">16-SEP-2003</passwd_2_end_date>
> <nspace xsi:type="xsd:string">1</nspace>
> <account_id
> xsi:type="xsd:string">0X000000250000000085</account_id>
> </DB_login>
> <DB_account xsi:type="ns1:DB_account"
> xmlns:ns1="http://localhost/axis/ws_login_view">
> <account_id
> xsi:type="xsd:string">0X000000250000000085</account_id>
> <status xsi:type="xsd:string">1</status>
> <begin_date xsi:type="xsd:string">17-SEP-2000</begin_date>
> <end_date xsi:type="xsd:string">31-DEC-2030</end_date>
> <unavailable_date
> xsi:type="xsd:string">NULL</unavailable_date>
> <account_poid xsi:type="xsd:string">0 0.0.0.1 / account
> 000001</account_poid>
> <CLID_requested xsi:type="xsd:string">0</CLID_requested>
> </DB_account>
> <ArrayOfDB_serviceArray
> xmlns:enc="http://www.w3.org/2001/06/soap-encoding"
> xmlns:ns1="http://localhost/axis/ws_login_view"
> enc:arrayType="ns1:ArrayOfDB_service[3]">
> <DB_service>
> <service_id
> xsi:type="xsd:string">0x00000002500000285</service_id>
> <service_name xsi:type="xsd:string">MAIN</service_name>
> <begin_date
> xsi:type="xsd:string">16-SEP-1996</begin_date>
> <end_date xsi:type="xsd:string">31-DEC-2030</end_date>
> <unavailable_date
> xsi:type="xsd:string">NULL</unavailable_date>
> <creation_date
> xsi:type="xsd:string">16-DEC-1996</creation_date>
> <account_id
> xsi:type="xsd:string">0X000000250000000085</account_id>
> <login_id
> xsi:type="xsd:string">0X000000250000000185</login_id>
> </DB_service>
> <DB_service>
> <service_id
> xsi:type="xsd:string">0x00000002500000286</service_id>
> <service_name xsi:type="xsd:string">MAIN</service_name>
> <begin_date
> xsi:type="xsd:string">16-SEP-1996</begin_date>
> <end_date xsi:type="xsd:string">31-DEC-2030</end_date>
> <unavailable_date
> xsi:type="xsd:string">NULL</unavailable_date>
> <creation_date
> xsi:type="xsd:string">16-DEC-1996</creation_date>
> <account_id
> xsi:type="xsd:string">0X000000250000000085</account_id>
> <login_id
> xsi:type="xsd:string">0X000000250000000185</login_id>
> </DB_service>
> <DB_service>
> <service_id
> xsi:type="xsd:string">0x00000002500000287</service_id>
> <service_name xsi:type="xsd:string">MAIN</service_name>
> <begin_date
> xsi:type="xsd:string">16-SEP-1996</begin_date>
> <end_date xsi:type="xsd:string">31-DEC-2030</end_date>
> <unavailable_date
> xsi:type="xsd:string">NULL</unavailable_date>
> <creation_date
> xsi:type="xsd:string">16-DEC-1996</creation_date>
> <end_date xsi:type="xsd:string">31-DEC-2030</end_date>
> <unavailable_date
> xsi:type="xsd:string">NULL</unavailable_date>
> <creation_date
> xsi:type="xsd:string">16-DEC-1996</creation_date>
> <account_id
> xsi:type="xsd:string">0X000000250000000085</account_id>
> <login_id
> xsi:type="xsd:string">0X000000250000000185</login_id>
> </DB_service>
> </ArrayOfDB_serviceArray>
> </ws_LOGIN_VIEW_out>
> </ns1:processGTCQueryResponse>
> </SOAP-ENV:Body>
>
=== message truncated ===
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com