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/04 02:48:16 UTC
[jira] Created: (AXIS2-661) WSDL2Java generates wrong build.xml
when jaxme option is used
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
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
[jira] Commented: (AXIS2-661) WSDL2Java generates wrong build.xml
when jaxme option is used
Posted by "Thilo Frotscher (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-661?page=comments#action_12378353 ]
Thilo Frotscher commented on AXIS2-661:
---------------------------------------
PS: The above issues apply to Axis2 1.0 final as well.
> 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
[jira] Resolved: (AXIS2-661) WSDL2Java generates wrong build.xml
when jaxme option is used
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-661?page=all ]
Davanum Srinivas resolved AXIS2-661.
------------------------------------
Resolution: Invalid
Thilo,
Please try latest nightly and let us know if this class loading problem still exists, then i can reopen the bug.
thanks,
dims
> 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)
> Issue Type: Bug
> Components: Tools
> Environment: Axis2 1.0 RC5
> Reporter: Thilo Frotscher
> Assigned To: 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
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-661) WSDL2Java generates wrong build.xml
when jaxme option is used
Posted by "Thilo Frotscher (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (AXIS2-661) WSDL2Java generates wrong build.xml
when jaxme option is used
Posted by "Thilo Frotscher (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (AXIS2-661) WSDL2Java generates wrong build.xml
when jaxme option is used
Posted by "Ajith Harshana Ranabahu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-661?page=comments#action_12414803 ]
Ajith Harshana Ranabahu commented on AXIS2-661:
-----------------------------------------------
The second issue seems to be a class loader issue to me since the failure occurs while trying to load resources from the aar.
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-661) WSDL2Java generates wrong build.xml
when jaxme option is used
Posted by "Sanjiva Weerawarana (JIRA)" <ji...@apache.org>.
[ 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
[jira] Assigned: (AXIS2-661) WSDL2Java generates wrong build.xml
when jaxme option is used
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-661?page=all ]
Deepal Jayasinghe reassigned AXIS2-661:
---------------------------------------
Assign To: Ajith Harshana Ranabahu
> 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