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 "Thilo Frotscher (JIRA)" <ji...@apache.org> on 2006/05/08 04:13:22 UTC
[jira] Commented: (AXIS2-661) WSDL2Java generates wrong build.xml
when jaxme option is used
[ http://issues.apache.org/jira/browse/AXIS2-661?page=comments#action_12378352 ]
Thilo Frotscher commented on AXIS2-661:
---------------------------------------
There's one more issue: in case of jaxme databinding it is not sufficient to deploy the aar file that was generated by the build.xml. For some reason the server can't find the class files and configuration files for jaxme when the service is invoked. Therefore, I had to copy all class files and config file to webapps/classes in addition to deploying the aar file. After that, the service worked fine...
> 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