You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Gladwin (JIRA)" <ji...@apache.org> on 2011/01/22 00:46:43 UTC
[jira] Created: (CXF-3269) nice to have a tool xsd2java
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.
[jira] Commented: (CXF-3269) nice to have a tool xsd2java
Posted by "Gladwin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985116#action_12985116 ]
Gladwin commented on CXF-3269:
------------------------------
Yes I am aware of same. I was looking forward to have command-line tool. Maven is great but not everyone uses it. Further more, schema can have multiple namespace, xjc cannot help to customise package for each namespace.
> 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.
[jira] Commented: (CXF-3269) nice to have a tool xsd2java
Posted by "Glen Mazza (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005627#comment-13005627 ]
Glen Mazza commented on CXF-3269:
---------------------------------
Gladwin, we're just providing a Maven plugin wrapper to the JAXB xjc tool (a wrapper, due to improvements in JAXB's own Maven plugin, which is largely no longer needed.) Have you also made these command-line enhancement requests to the JAXB team (JAXB has its own JIRA) for them to improve their xjc tool with these additional options? Have you also checked the JAXB user's list to confirm you do not have the options within XJC you presently require? XJC has a lot of options of which you may be unaware: http://www.jroller.com/gmazza/entry/customizing_jaxb_artifacts . From what I'm reading, you're assuming the JAXB team won't help you so you're not bothering to contact them, and then hoping that we will develop an XJC replacement, which is really out of scope for the CXF project. Further, the verbose options you're asking for are almost invariably configured today via Maven or Ant (so people don't have to try to recall from memory), and not typed via command line, so I don't see much demand for what you're asking for.
> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CXF-3269) nice to have a tool xsd2java
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CXF-3269) nice to have a tool xsd2java
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp updated CXF-3269:
-----------------------------
Fix Version/s: (was: 2.3.4)
(was: 2.3.3)
(was: 2.2.13)
(was: 2.4)
> 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
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira