[jira] Commented: (AXIS2-2814) XSI:TYPE not being generated for SOAP JMS client requests
[ 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2814) XSI:TYPE not being generated for SOAP JMS client requests
[ 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2814) XSI:TYPE not being generated for SOAP JMS client requests
[ 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2814) XSI:TYPE not being generated for SOAP JMS client requests
[ 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2814) XSI:TYPE not being generated for SOAP JMS client requests
[ 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-2814) XSI:TYPE not being generated for SOAP JMS client requests
[ 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
