[ 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]