[
https://issues.apache.org/jira/browse/AXIS2-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598761#comment-13598761
]
Nicolae Petridean edited comment on AXIS2-5249 at 3/11/13 12:38 PM:
--------------------------------------------------------------------
Hi guys,
is there a way to avoid this by keeping jaxbri as databinding provider?
I've tried 1.7.0 snapshot , but it is not a working solution yet.
Best regards, Nicu
was (Author: nicolae.petridean):
Hi guys,
is there a way to avoid this by keeping jaxbri as databinding provider?
I've tried 1.7.0 snapshot , but it is a working solution yet.
Best regards, Nicu
> Axis2 1.6.1 generates invalid request when using JAXBRI bindings
> ----------------------------------------------------------------
>
> Key: AXIS2-5249
> URL: https://issues.apache.org/jira/browse/AXIS2-5249
> Project: Axis2
> Issue Type: Bug
> Components: databinding
> Affects Versions: 1.6.1
> Environment: Windows, Solaris
> Reporter: Dmitriy
> Assignee: Andreas Veithen
> Fix For: 1.7.0
>
> Attachments: build.xml, ESubServices.wsdl, ESubServices.wsdl,
> ESubTest.java
>
>
> The client generated using JAXBRI bindings creates invalid request XML with
> version 1.6.1. The same code works with Axis 2 1.5.1 using JAXBRI bindings
> and Axis 2 1.6.1 using ADB bindings.
> This problem seems to impact several clients for various Web Services. All
> clients were working fine with Axis 2 1.5.1.
> I will attach WSDL, test client, and code generation commands to this ticket.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]
