axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Mattox (JIRA)" <>
Subject [jira] Commented: (AXIS2-3055) add an option not to generate xmlbeans classes and instead get them from classpath
Date Fri, 03 Aug 2007 08:13:52 GMT


Michael Mattox commented on AXIS2-3055:

This sounds like a good approach.  As it is now, all the xmlbeans related files (classes +
resources) are mixed with the axis2 specific code.  It'd be good to separate them into separate
directories (and jar the xmlbeans files) so that we can easily delete the xmlbeans code and
replace it with another.

> add an option not to generate xmlbeans classes and instead get them from classpath
> ----------------------------------------------------------------------------------
>                 Key: AXIS2-3055
>                 URL:
>             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 (,
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:
For additional commands, e-mail:

View raw message