[ http://issues.apache.org/jira/browse/AXIS2-661?page=comments#action_12378376 ]
Thilo Frotscher commented on AXIS2-661: --------------------------------------- Sorry, I think my comment was mistakable. It's not the jaxme libraries (i.e. jar files) that the server can't find, but the generated files (classes, jaxb.properties, Configuration.xml). These files are contained in the aar file, but deploying the aar file is not enough: the same files have to be copied to webapps\axis2\WEB-INF\classes, otherwise there is an exception when the service is invoked. This way, the same files are deployed twice (aar file and classes folder) The other to issues reported in my first comment apply to Axis2 1.0 final as well. Thanks! > 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
