[ http://issues.apache.org/jira/browse/AXIS2-661?page=comments#action_12378366 ]
Sanjiva Weerawarana commented on AXIS2-661: ------------------------------------------- This goes back to a comment I made about another data binding issue (sorry forget the number): we can't possibly have all the jars for all possible data bindings in the core distributions. So similarly, when we codegen for some data bindings, the generated code must take a dependency on a jar that may not be in the core dist. Ideally we can put some stuff in build.xml to copy those jars over to the .aar at build time. > WSDL2Java generates wrong build.xml when jaxme option is used > ------------------------------------------------------------- > > Key: AXIS2-661 > URL: http://issues.apache.org/jira/browse/AXIS2-661 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: Tools > Environment: Axis2 1.0 RC5 > Reporter: Thilo Frotscher > Assignee: Ajith Harshana Ranabahu > > When WSDL2Java is used with the jaxme option for databinding , there are two > bugs: > - it generates a build.xml for the xmlbeans databinding instead for jaxme > - ns2p option does not seem to work for jaxme (but works fine for adb and > xmlbeans) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
