cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-3269) nice to have a tool xsd2java
Date Fri, 31 Mar 2017 17:07:41 GMT

     [ https://issues.apache.org/jira/browse/CXF-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Kulp resolved CXF-3269.
------------------------------
       Resolution: Won't Fix
    Fix Version/s: Invalid

Marking "won't fix" as it's not something we're likely to do as there is the xjc command built
into the JDK which works "ok".

> 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: Invalid
>
>
> 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 was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message