[
https://issues.apache.org/jira/browse/AXIS2-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400855#comment-13400855
]
Hudson commented on AXIS2-5147:
-------------------------------
Integrated in Axis2 #1592 (See [https://builds.apache.org/job/Axis2/1592/])
(Partially) reverted AXIS2-4197 (r1052896) to solve AXIS2-5147: the changes
caused the JAXBRI databinding to produce invalid messages (i.e. messages that
don't conform to the WSDL). (Revision 1353707)
Result = SUCCESS
veithen :
Files :
*
/axis/axis2/java/core/trunk/modules/jaxbri/src/main/resources/org/apache/axis2/jaxbri/template/JaxbRIDatabindingTemplate.xsl
*
/axis/axis2/java/core/trunk/modules/jaxbri/src/test/java/org/apache/axis2/jaxbri/processor/ProcessorTest.java
*
/axis/axis2/java/core/trunk/modules/jaxbri/src/test/resources/org/apache/axis2/jaxbri/processor/response.xml
> Regression 1.5.x -> 1.6.x, generated jaxbri Transaction processor is
> incompatible with client code, wrong top level element name used
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-5147
> URL: https://issues.apache.org/jira/browse/AXIS2-5147
> Project: Axis2
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.6.1
> Environment: Windows, Sun jdk 1.6.0_24, Axis 1.6.1
> Reporter: Mika Vesterholm
> Attachments: Transaction_1.33.wsdl, Transaction_1.33.xsd
>
>
> Following command generates TransactionProcessorMessageReceiverInOut which is
> incompatible with client.
> wsdl2java.bat -u -d jaxbri -sp -ss -p com.example.jaxb.soap -ns2p
> urn:schemas-example-com:transaction-data-1.33=com.example.
> jaxb.soap.mo -o src-generated -uri Transaction_1.33.wsdl
> Client code generated with command
> wsdl2java.bat -u -d adb -sp -o src-generated -uri Transaction_1.33.wsdl
> Now when calling generated service through
> TransactionProcessorStub.runTransaction reply body has top level element name
> runTransaction and not replyMessage.
> root cause is this line in the generated invokeBusinessLogic method
> envelope =
> toEnvelope(getSOAPFactory(msgContext), replyMessage1, false, new
> javax.xml.namespace.QName("urn:schemas-example-com:transaction-data:TransactionProcessor",
> "runTransaction"));
> Generated code works ok when I changed it to use same names as generated
> toOM(ReplyMessage, boolean). This old toOM is generated the same way both in
> 1.5 and 1.6 but in 1.6 it is dead code (private method which is not called at
> all).
> envelope =
> toEnvelope(getSOAPFactory(msgContext), replyMessage1, false, new
> javax.xml.namespace.QName("urn:schemas-example-com:transaction-data-1.33",
> "replyMessage"));
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]