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 "Mika Vesterholm (JIRA)" <ji...@apache.org> on 2011/09/19 12:02:08 UTC
[jira] [Created] (AXIS2-5147) Regression 1.5.x -> 1.6.x, generated
jaxbri Transaction processor is incompatible with client code, wrong top
level element name used
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
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] [Resolved] (AXIS2-5147) Regression 1.5.x -> 1.6.x, generated
jaxbri Transaction processor is incompatible with client code, wrong top
level element name used
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved AXIS2-5147.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.7.0
Assignee: Andreas Veithen
> 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
> Assignee: Andreas Veithen
> Fix For: 1.7.0
>
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] [Commented] (AXIS2-5147) Regression 1.5.x -> 1.6.x,
generated jaxbri Transaction processor is incompatible with client code,
wrong top level element name used
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] [Updated] (AXIS2-5147) Regression 1.5.x -> 1.6.x, generated
jaxbri Transaction processor is incompatible with client code, wrong top
level element name used
Posted by "Mika Vesterholm (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mika Vesterholm updated AXIS2-5147:
-----------------------------------
Attachment: Transaction_1.33.xsd
Transaction_1.33.wsdl
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] [Commented] (AXIS2-5147) Regression 1.5.x -> 1.6.x,
generated jaxbri Transaction processor is incompatible with client code,
wrong top level element name used
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400351#comment-13400351 ]
Hudson commented on AXIS2-5147:
-------------------------------
Integrated in Axis2 #1591 (See [https://builds.apache.org/job/Axis2/1591/])
Added unit tests providing evidence for AXIS2-5147. (Revision 1353394)
Result = SUCCESS
veithen :
Files :
* /axis/axis2/java/core/trunk/modules/jaxbri/pom.xml
* /axis/axis2/java/core/trunk/modules/jaxbri/src/test/java/org/apache/axis2/jaxbri/Test01Test.java
* /axis/axis2/java/core/trunk/modules/jaxbri/src/test/java/org/apache/axis2/jaxbri/processor
* /axis/axis2/java/core/trunk/modules/jaxbri/src/test/java/org/apache/axis2/jaxbri/processor/ProcessorImpl.java
* /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
* /axis/axis2/java/core/trunk/modules/jaxbri/src/test/resources/org
* /axis/axis2/java/core/trunk/modules/jaxbri/src/test/resources/org/apache
* /axis/axis2/java/core/trunk/modules/jaxbri/src/test/resources/org/apache/axis2
* /axis/axis2/java/core/trunk/modules/jaxbri/src/test/resources/org/apache/axis2/jaxbri
* /axis/axis2/java/core/trunk/modules/jaxbri/src/test/resources/org/apache/axis2/jaxbri/processor
* /axis/axis2/java/core/trunk/modules/jaxbri/src/test/resources/org/apache/axis2/jaxbri/processor/request.xml
* /axis/axis2/java/core/trunk/modules/jaxbri/src/test/resources/org/apache/axis2/jaxbri/processor/response.xml
* /axis/axis2/java/core/trunk/modules/jaxbri/src/test/wsdl/processor.wsdl
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org