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 "balaji iyer (JIRA)" <ji...@apache.org> on 2007/06/18 06:24:25 UTC
[jira] Created: (AXIS2-2814) XSI:TYPE not being generated for SOAP
JMS client requests
XSI:TYPE not being generated for SOAP JMS client requests
---------------------------------------------------------
Key: AXIS2-2814
URL: https://issues.apache.org/jira/browse/AXIS2-2814
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.2
Environment: Win XP, AXIS2 (1.2)
Reporter: balaji iyer
I'm trying to run the SOAP JMS webservice which is hosted in businessworks.
I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding.
However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP.
The issues is that the "xsi type" is not being generated for JMS requests.
Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-2814) XSI:TYPE not being generated for SOAP
JMS client requests
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas resolved AXIS2-2814.
-------------------------------------
Resolution: Fixed
> XSI:TYPE not being generated for SOAP JMS client requests
> ---------------------------------------------------------
>
> Key: AXIS2-2814
> URL: https://issues.apache.org/jira/browse/AXIS2-2814
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Win XP, AXIS2 (1.2)
> Reporter: balaji iyer
> Assignee: Amila Chinthaka Suriarachchi
> Attachments: AXIS2-2814-no-headers.zip, SOAPJMSAxisXSITypeLost_Bug.zip
>
>
> I'm trying to run the SOAP JMS webservice which is hosted in businessworks.
> I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding.
> However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP.
> The issues is that the "xsi type" is not being generated for JMS requests.
> Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2814) XSI:TYPE not being generated for
SOAP JMS client requests
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507108 ]
Davanum Srinivas commented on AXIS2-2814:
-----------------------------------------
Balaji,
I checked in a fix to XmlSchema, if you can't wait for that, please drop latest xerces jar into your jre's endorsed directory. As Amila said, the original problem is fixed hence i am closing this bug.
thanks,
dims
> XSI:TYPE not being generated for SOAP JMS client requests
> ---------------------------------------------------------
>
> Key: AXIS2-2814
> URL: https://issues.apache.org/jira/browse/AXIS2-2814
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Win XP, AXIS2 (1.2)
> Reporter: balaji iyer
> Assignee: Amila Chinthaka Suriarachchi
> Attachments: AXIS2-2814-no-headers.zip, SOAPJMSAxisXSITypeLost_Bug.zip
>
>
> I'm trying to run the SOAP JMS webservice which is hosted in businessworks.
> I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding.
> However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP.
> The issues is that the "xsi type" is not being generated for JMS requests.
> Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2814) XSI:TYPE not being generated for
SOAP JMS client requests
Posted by "balaji iyer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507138 ]
balaji iyer commented on AXIS2-2814:
------------------------------------
Hi Dims, Amila,
After replacing the Xerces Implmentation in the endorsed folder in the
JRE and generating the Stubs, I receive the following error in my client
code.
Is this something new ?
Exception in thread "main" org.apache.axis2.AxisFault: Transport out has
not been set
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:379)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
ation.java:380)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInA
xisOperation.java:202)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:142
)
at
com.citi.serviceclient.ThailandServiceJmsStub.CardStatementOp(ThailandSe
rviceJmsStub.java:163)
rgds....
Balaji
> XSI:TYPE not being generated for SOAP JMS client requests
> ---------------------------------------------------------
>
> Key: AXIS2-2814
> URL: https://issues.apache.org/jira/browse/AXIS2-2814
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Win XP, AXIS2 (1.2)
> Reporter: balaji iyer
> Assignee: Amila Chinthaka Suriarachchi
> Attachments: AXIS2-2814-no-headers.zip, SOAPJMSAxisXSITypeLost_Bug.zip
>
>
> I'm trying to run the SOAP JMS webservice which is hosted in businessworks.
> I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding.
> However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP.
> The issues is that the "xsi type" is not being generated for JMS requests.
> Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2814) XSI:TYPE not being generated for SOAP
JMS client requests
Posted by "balaji iyer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
balaji iyer updated AXIS2-2814:
-------------------------------
In the nightly build "axis2-SNAPSHOT"
I get the following Exception "NoSuchMethodError". Below is its stack trace.
Exception in thread "main" java.lang.NoSuchMethodError: org.w3c.dom.Document.getInputEncoding()Ljava/lang/String;
at org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:80)
at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:355)
at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:300)
at org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1878)
at org.apache.ws.commons.schema.SchemaBuilder.handleInclude(SchemaBuilder.java:1661)
at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:166)
at org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:79)
at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:355)
at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:300)
at org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1878)
at org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1614)
at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:172)
at org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:79)
at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:355)
at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:300)
at org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1878)
at org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1896)
at org.apache.ws.commons.schema.SchemaBuilder.handleInclude(SchemaBuilder.java:1668)
at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:166)
at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:343)
at org.apache.axis2.description.WSDLToAxisServiceBuilder.getXMLSchema(WSDLToAxisServiceBuilder.java:137)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.copyExtensibleElements(WSDL11ToAxisServiceBuilder.java:1949)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:261)
at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateAllServices(WSDL11ToAllAxisServicesBuilder.java:100)
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerationEngine.java:131)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
> XSI:TYPE not being generated for SOAP JMS client requests
> ---------------------------------------------------------
>
> Key: AXIS2-2814
> URL: https://issues.apache.org/jira/browse/AXIS2-2814
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Win XP, AXIS2 (1.2)
> Reporter: balaji iyer
> Assignee: Amila Chinthaka Suriarachchi
> Attachments: AXIS2-2814-no-headers.zip, SOAPJMSAxisXSITypeLost_Bug.zip
>
>
> I'm trying to run the SOAP JMS webservice which is hosted in businessworks.
> I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding.
> However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP.
> The issues is that the "xsi type" is not being generated for JMS requests.
> Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2814) XSI:TYPE not being generated for SOAP
JMS client requests
Posted by "balaji iyer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
balaji iyer updated AXIS2-2814:
-------------------------------
This is default ADB.
> XSI:TYPE not being generated for SOAP JMS client requests
> ---------------------------------------------------------
>
> Key: AXIS2-2814
> URL: https://issues.apache.org/jira/browse/AXIS2-2814
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Win XP, AXIS2 (1.2)
> Reporter: balaji iyer
>
> I'm trying to run the SOAP JMS webservice which is hosted in businessworks.
> I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding.
> However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP.
> The issues is that the "xsi type" is not being generated for JMS requests.
> Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Issue Comment Edited: (AXIS2-2814) XSI:TYPE not being
generated for SOAP JMS client requests
Posted by "balaji iyer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505709 ]
balaji iyer edited comment on AXIS2-2814 at 6/18/07 9:56 AM:
-------------------------------------------------------------
Pls find the attachment containing test code, soap request format(Axis-Http-SOAP-Request.txt and Axis-JMS-SOAP-Request.txt), wsdl and schemas over which axis wsdl2java is being used.
Axis-Http-SOAP-Request(SOAP BODY) seems to be fine. The information does not contain qualified namespace information. The local names follow the parent namespace. The XSI types are correctly defined in the SOAP Request.
For Axis-JMS-SOAP-Request, this is not the case
> XSI:TYPE not being generated for SOAP JMS client requests
> ---------------------------------------------------------
>
> Key: AXIS2-2814
> URL: https://issues.apache.org/jira/browse/AXIS2-2814
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Win XP, AXIS2 (1.2)
> Reporter: balaji iyer
> Attachments: SOAPJMSAxisXSITypeLost_Bug.zip
>
>
> I'm trying to run the SOAP JMS webservice which is hosted in businessworks.
> I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding.
> However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP.
> The issues is that the "xsi type" is not being generated for JMS requests.
> Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2814) XSI:TYPE not being generated for
SOAP JMS client requests
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505665 ]
Davanum Srinivas commented on AXIS2-2814:
-----------------------------------------
Please upload your sample code / soap messages / wsdl / xsd's. Anything else that will help us recreate the issue
thanks,
dims
> XSI:TYPE not being generated for SOAP JMS client requests
> ---------------------------------------------------------
>
> Key: AXIS2-2814
> URL: https://issues.apache.org/jira/browse/AXIS2-2814
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Win XP, AXIS2 (1.2)
> Reporter: balaji iyer
>
> I'm trying to run the SOAP JMS webservice which is hosted in businessworks.
> I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding.
> However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP.
> The issues is that the "xsi type" is not being generated for JMS requests.
> Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-2814) XSI:TYPE not being generated for SOAP
JMS client requests
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas resolved AXIS2-2814.
-------------------------------------
Resolution: Fixed
Balaji,
Please don't reuse this jira for later issues. which are totally unrelated to the original problem.
thanks,
dims
> XSI:TYPE not being generated for SOAP JMS client requests
> ---------------------------------------------------------
>
> Key: AXIS2-2814
> URL: https://issues.apache.org/jira/browse/AXIS2-2814
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Win XP, AXIS2 (1.2)
> Reporter: balaji iyer
> Assignee: Amila Chinthaka Suriarachchi
> Attachments: AXIS2-2814-no-headers.zip, SOAPJMSAxisXSITypeLost_Bug.zip
>
>
> I'm trying to run the SOAP JMS webservice which is hosted in businessworks.
> I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding.
> However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP.
> The issues is that the "xsi type" is not being generated for JMS requests.
> Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Reopened: (AXIS2-2814) XSI:TYPE not being generated for SOAP
JMS client requests
Posted by "balaji iyer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
balaji iyer reopened AXIS2-2814:
--------------------------------
Sorry for re-opening this issue but, now the nightly build throws an error for soap/jms binding that
"Transport type is not set"
> XSI:TYPE not being generated for SOAP JMS client requests
> ---------------------------------------------------------
>
> Key: AXIS2-2814
> URL: https://issues.apache.org/jira/browse/AXIS2-2814
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Win XP, AXIS2 (1.2)
> Reporter: balaji iyer
> Assignee: Amila Chinthaka Suriarachchi
> Attachments: AXIS2-2814-no-headers.zip, SOAPJMSAxisXSITypeLost_Bug.zip
>
>
> I'm trying to run the SOAP JMS webservice which is hosted in businessworks.
> I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding.
> However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP.
> The issues is that the "xsi type" is not being generated for JMS requests.
> Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2814) XSI:TYPE not being generated for SOAP
JMS client requests
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS2-2814:
------------------------------------
Attachment: AXIS2-2814-no-headers.zip
Amila,
When i run wsdl2java, method CardStatementOp, there should be 2 parameters, one for TestReq3 and one for MsgHeader. latest svn does not generate the parameter for the header. Can you please take a look?
thanks,
dims
> XSI:TYPE not being generated for SOAP JMS client requests
> ---------------------------------------------------------
>
> Key: AXIS2-2814
> URL: https://issues.apache.org/jira/browse/AXIS2-2814
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Win XP, AXIS2 (1.2)
> Reporter: balaji iyer
> Attachments: AXIS2-2814-no-headers.zip, SOAPJMSAxisXSITypeLost_Bug.zip
>
>
> I'm trying to run the SOAP JMS webservice which is hosted in businessworks.
> I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding.
> However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP.
> The issues is that the "xsi type" is not being generated for JMS requests.
> Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2814) XSI:TYPE not being generated for SOAP
JMS client requests
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS2-2814:
------------------------------------
Assignee: Amila Chinthaka Suriarachchi
> XSI:TYPE not being generated for SOAP JMS client requests
> ---------------------------------------------------------
>
> Key: AXIS2-2814
> URL: https://issues.apache.org/jira/browse/AXIS2-2814
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Win XP, AXIS2 (1.2)
> Reporter: balaji iyer
> Assignee: Amila Chinthaka Suriarachchi
> Attachments: AXIS2-2814-no-headers.zip, SOAPJMSAxisXSITypeLost_Bug.zip
>
>
> I'm trying to run the SOAP JMS webservice which is hosted in businessworks.
> I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding.
> However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP.
> The issues is that the "xsi type" is not being generated for JMS requests.
> Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2814) XSI:TYPE not being generated for
SOAP JMS client requests
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506571 ]
Amila Chinthaka Suriarachchi commented on AXIS2-2814:
-----------------------------------------------------
this is an code generation time issue. What is the jdk you use? can you try with the earlier jdk with which you could generate the code correctly.
> XSI:TYPE not being generated for SOAP JMS client requests
> ---------------------------------------------------------
>
> Key: AXIS2-2814
> URL: https://issues.apache.org/jira/browse/AXIS2-2814
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Win XP, AXIS2 (1.2)
> Reporter: balaji iyer
> Assignee: Amila Chinthaka Suriarachchi
> Attachments: AXIS2-2814-no-headers.zip, SOAPJMSAxisXSITypeLost_Bug.zip
>
>
> I'm trying to run the SOAP JMS webservice which is hosted in businessworks.
> I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding.
> However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP.
> The issues is that the "xsi type" is not being generated for JMS requests.
> Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2814) XSI:TYPE not being generated for
SOAP JMS client requests
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505663 ]
Davanum Srinivas commented on AXIS2-2814:
-----------------------------------------
Let me guess, this is xmlbeans databinding?
> XSI:TYPE not being generated for SOAP JMS client requests
> ---------------------------------------------------------
>
> Key: AXIS2-2814
> URL: https://issues.apache.org/jira/browse/AXIS2-2814
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Win XP, AXIS2 (1.2)
> Reporter: balaji iyer
>
> I'm trying to run the SOAP JMS webservice which is hosted in businessworks.
> I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding.
> However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP.
> The issues is that the "xsi type" is not being generated for JMS requests.
> Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Issue Comment Edited: (AXIS2-2814) XSI:TYPE not being
generated for SOAP JMS client requests
Posted by "balaji iyer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507166 ]
balaji iyer edited comment on AXIS2-2814 at 6/22/07 1:44 AM:
-------------------------------------------------------------
Sorry for re-opening this issue but, now the nightly build throws an error for soap/jms binding that
"Transport out is not set"
was:
Sorry for re-opening this issue but, now the nightly build throws an error for soap/jms binding that
"Transport type is not set"
> XSI:TYPE not being generated for SOAP JMS client requests
> ---------------------------------------------------------
>
> Key: AXIS2-2814
> URL: https://issues.apache.org/jira/browse/AXIS2-2814
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Win XP, AXIS2 (1.2)
> Reporter: balaji iyer
> Assignee: Amila Chinthaka Suriarachchi
> Attachments: AXIS2-2814-no-headers.zip, SOAPJMSAxisXSITypeLost_Bug.zip
>
>
> I'm trying to run the SOAP JMS webservice which is hosted in businessworks.
> I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding.
> However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP.
> The issues is that the "xsi type" is not being generated for JMS requests.
> Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2814) XSI:TYPE not being generated for
SOAP JMS client requests
Posted by "balaji iyer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506749 ]
balaji iyer commented on AXIS2-2814:
------------------------------------
Hello Amila,
I am using JDK 1.42. The JDK used is the same for both scenarios
soap/HTTP and soap/JMS.
I doubt if this related to jdk. The problem of XSI type not being
generated for soap/jms for some tag is a bug. The nightly build which
you mentioned fixes the problem does not run correctly for the same wsdl
and same jdk.
Pls. advise how can I make this work if the bug is already fixed in the
nightly build.
As of now, the night build gives me a noSuchMethod Error. The stacktrace
is provided in my earlier comment
Thanks,
Balaji
> XSI:TYPE not being generated for SOAP JMS client requests
> ---------------------------------------------------------
>
> Key: AXIS2-2814
> URL: https://issues.apache.org/jira/browse/AXIS2-2814
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Win XP, AXIS2 (1.2)
> Reporter: balaji iyer
> Assignee: Amila Chinthaka Suriarachchi
> Attachments: AXIS2-2814-no-headers.zip, SOAPJMSAxisXSITypeLost_Bug.zip
>
>
> I'm trying to run the SOAP JMS webservice which is hosted in businessworks.
> I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding.
> However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP.
> The issues is that the "xsi type" is not being generated for JMS requests.
> Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2814) XSI:TYPE not being generated for
SOAP JMS client requests
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506293 ]
Amila Chinthaka Suriarachchi commented on AXIS2-2814:
-----------------------------------------------------
I fixed an issue with the ADBXMLStreamReaderImpl which must have caused your problme. Can you please check with a nightly build?
> XSI:TYPE not being generated for SOAP JMS client requests
> ---------------------------------------------------------
>
> Key: AXIS2-2814
> URL: https://issues.apache.org/jira/browse/AXIS2-2814
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Win XP, AXIS2 (1.2)
> Reporter: balaji iyer
> Assignee: Amila Chinthaka Suriarachchi
> Attachments: AXIS2-2814-no-headers.zip, SOAPJMSAxisXSITypeLost_Bug.zip
>
>
> I'm trying to run the SOAP JMS webservice which is hosted in businessworks.
> I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes. There are no issues for HTTP binding.
> However for JMS binding the generated code seems to be having the following issue. It seems that AXIS2 is generating different soap request (payload) for JMS and HTTP.
> The issues is that the "xsi type" is not being generated for JMS requests.
> Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them consistently in businessworks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org