[
https://issues.apache.org/jira/browse/AXIS2-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi resolved AXIS2-3055.
-------------------------------------------------
Resolution: Fixed
added a new parameter -Ewdc to generate with a dummy schema. then you can
replace this with the correct xmlbeans generated code.
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
