You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2011/01/22 03:49:43 UTC

[jira] Commented: (CXF-3269) nice to have a tool xsd2java

    [ https://issues.apache.org/jira/browse/CXF-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985039#action_12985039 ] 

Freeman Fang commented on CXF-3269:
-----------------------------------

Hi,

FYI, cxf already have a cxf xjc plugin[1] which wrap jaxb xjc tool,  this plugin has xsd2java goal and can specify more options lie package name.
I guess this is what you want, right?

[1]http://cxf.apache.org/cxf-xjc-plugin.html

Freeman


> nice to have a tool xsd2java
> ----------------------------
>
>                 Key: CXF-3269
>                 URL: https://issues.apache.org/jira/browse/CXF-3269
>             Project: CXF
>          Issue Type: Wish
>          Components: Tooling
>            Reporter: Gladwin
>            Priority: Minor
>             Fix For: 2.2.13, 2.4, 2.3.3, 2.3.4
>
>
> In a scenario where by multiple wsdl's refer to same schema, it would be nice to separate the process of generating service from WSDL (with option {{-nexclude schema-namespace [=java-packagename]}}) v/s generating JAXB mapping POJOs with {{xsd2java}}.
> For this we would need a  tool *xsd2java* which is similar to *wsdl2java* but instead would generate java code from XSD URL. {{xjc}} tool that comes with JDK will do the trick but does not have advance options like multiple {{-p [ wsdl-namespace= ] PackageName}}, {{-autoNameResolution}}, etc.
> Further more this will help CXF to be used in non webservice scenarios where XML data exchange takes place and JAXB mapping POJOs needs to be generated from XSD.

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