[
https://issues.apache.org/jira/browse/AXIS2-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Barrs updated AXIS2-4269:
--------------------------------
Summary: Axis2 - XMLBeans path naming inconsistencies (was: Axis2 -
XMLBeasn path naming inconsistencies)
> Axis2 - XMLBeans path naming inconsistencies
> --------------------------------------------
>
> Key: AXIS2-4269
> URL: https://issues.apache.org/jira/browse/AXIS2-4269
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: Tools
> Affects Versions: 1.4.1
> Environment: Windows
> Reporter: Martin Barrs
>
> I am using Axis2 1.4 and XMLBeans 2.4. I would like to use XMLBeans ant task
> to generate all the XMLBeans artifacts and use Axis2 to just generate the
> skels and stubs. This is because I have a mix of .wsdl's and .xsd's I need to
> generate and would like to normalize the resource files. The files are also
> very dynamic, hence I cannot use namespace remapping as a workaround.
> What I've found is, though, that the Axis2 tasks and XMLBeans tasks name
> entities differently when a span in the entity path starts with a number. For
> example:
> Element namespace - com/example/testService/2009/03
> Schema - com/example/testService/2009/03/myTestSchema
> XMLBeans generated element -
> com.example.testService.x2009.x03.myTestSchema
> Axis2 generated element - com.example.testService._2009._03.myTestSchema
> Note that XMLbeans prepends 'x' and Axis2 '_' to numeric paths - this is the
> issue!
> So, if I use wsdl2java to generate skels/stubs with -Ewsd, this difference
> changes the resource index mapping making it impossible to use the separately
> generated files.
> The solution would be for XMLBeans and Axis to have the same prefix for
> numeric path elements, or at least have the ability to specify a default.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
