You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by bu...@apache.org on 2003/03/05 13:09:22 UTC
DO NOT REPLY [Bug 17670] New: -
Interoperability of WSIF with JAX-RPC module in Sun One Studio.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17670>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17670
Interoperability of WSIF with JAX-RPC module in Sun One Studio.
Summary: Interoperability of WSIF with JAX-RPC module in Sun One
Studio.
Product: Axis-WSIF
Version: current (nightly)
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Critical
Priority: Other
Component: Basic Architecture
AssignedTo: axis-dev@ws.apache.org
ReportedBy: st_patil@hotmail.com
CC: st_patil@hotmail.com
By using dynamic Invoker sample example (Apache or Axis DynamicProvider) of
WSIF 2.0rc1 to invoke Webservice generated by Sun One Studio webservice Module
(JAX-RPC impl.) it produce the following Exception on the server side
[ERROR] http - -transformation failed <transformation failed>
deserialization error: unexpected XML reader state. expected:
END but found: START: {urn:HelloWorld/wsdl}String_1
at com.sun.xml.rpc.encoding.ObjectSerializerBase.deserialize
(ObjectSerializerBase.java:202)
at com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.deserialize
(ReferenceableSerializerImpl.java:115)
But if SoapRMI DynamicProvider used instead of Apache or Axis it works fine.
So Can Any body tell, Where it goes wrong?
I also have another doubt.As WSIF is a framework for invoking WSDL-described
services.How can I know which Dynamic provider used to invoke the Web Service?
Waiting for response,
Regards,
Sachin.