axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amila Chinthaka Suriarachchi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-3055) add an option not to generate xmlbeans classes and instead get them from classpath
Date Thu, 02 Aug 2007 11:11:52 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517213
] 

Amila Chinthaka Suriarachchi commented on AXIS2-3055:
-----------------------------------------------------

This is something I was thinking about to solve some problems created by xmlbeans and jaxbri
databindings. Actually what we can do is to generate the a dummy schema only with the element
name (just what now you try to do manually) and compile with that schema. 
This way wsdl2java can generate Axis2 specific file and later user can replace the Axis2 generated
files with the directly generated java files (and resources). 
Definitely we will add this from next release.

> add an option not to generate xmlbeans classes and instead get them from classpath
> ----------------------------------------------------------------------------------
>
>                 Key: AXIS2-3055
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3055
>             Project: Axis 2.0 (Axis2)
>          Issue Type: New Feature
>    Affects Versions: 1.2
>            Reporter: Michael Mattox
>            Assignee: Amila Chinthaka Suriarachchi
>            Priority: Minor
>
> With XFire, when generating the java code from the WSDL, XFire looks on the classpath
for the xmlbeans and if they're there, XFire does not generate them.   This would be very
useful with Axis2.  At the moment, I do not believe there is any way to avoid having Axis2
generate the xmlbeans classes.  
> In my particular case I found a bug with this generation (https://issues.apache.org/jira/browse/AXIS2-3048),
and the workaround is to empty out all my elements and complex types and use wsdl2java and
then generate the classes from the real schemas with xmlbeans.  Kind of cumbersome.
> I prefer to have xmlbeans generate my classes and axis2 generate the web service related
files.  That way I keep the two separate.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message