[
https://issues.apache.org/jira/browse/CXF-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phan Hoan Vu updated CXF-4477:
------------------------------
Description:
In org.apache.cxf.tools.wadlto.jaxrs.SourceGenerator we have the code like this:
XSD_SPECIFIC_TYPE_MAP = new HashMap<String, String>();
XSD_SPECIFIC_TYPE_MAP.put("string", "String");
XSD_SPECIFIC_TYPE_MAP.put("decimal", "java.math.BigInteger");
XSD_SPECIFIC_TYPE_MAP.put("integer", "long");
If we have a wadl like this:
<param name="param1" required="true" style="query" type="xs:int" />
<param name="param2" required="true" style="query" type="xs:long" />
it's always generate (String param1) and (String param2)
So far as I know, xs:int and xs:long beside xs:string are the most usage type
in WADL. But now it can not work any more!!!!
I think this is a regression bug from
**********************************************************
sergeyb 08.05.12 19:25:44
[CXF-4292] Defaulting to String when WADL Generator can not determine a class
name of the primitive type
**********************************************************
For the solution, I think we can expand XSD_SPECIFIC_TYPE_MAP which the exactly
mapping as a standard:
http://en.wikipedia.org/wiki/Java_Architecture_for_XML_Binding
Could you please have a look on this issue.
Many many many thanks :)
was:
In org.apache.cxf.tools.wadlto.jaxrs.SourceGenerator we have the code like this:
XSD_SPECIFIC_TYPE_MAP = new HashMap<String, String>();
XSD_SPECIFIC_TYPE_MAP.put("string", "String");
XSD_SPECIFIC_TYPE_MAP.put("decimal", "java.math.BigInteger");
XSD_SPECIFIC_TYPE_MAP.put("integer", "long");
If we have a wadl like this:
<param name="param1" required="true" style="query" type="xs:int" />
<param name="param2" required="true" style="query" type="xs:long" />
it's always generate (String param1) and (String param2)
So far as I know, xs:int and xs:long beside xs:string are the most usage type
in WADL. But know it can not work any more!!!!
I think this is a regression bug from
**********************************************************
sergeyb 08.05.12 19:25:44
[CXF-4292] Defaulting to String when WADL Generator can not determine a class
name of the primitive type
**********************************************************
For the solution, I think we can expand XSD_SPECIFIC_TYPE_MAP which the exactly
mapping as a standard:
http://en.wikipedia.org/wiki/Java_Architecture_for_XML_Binding
Could you please have a look on this issue.
Many many many thanks :)
> [WADL2JAVA] Generate incorrect primitive parameter type
> --------------------------------------------------------
>
> Key: CXF-4477
> URL: https://issues.apache.org/jira/browse/CXF-4477
> Project: CXF
> Issue Type: Bug
> Components: JAXB Databinding, Tooling, WS-* Components
> Affects Versions: 2.6.1
> Reporter: Phan Hoan Vu
> Priority: Critical
>
> In org.apache.cxf.tools.wadlto.jaxrs.SourceGenerator we have the code like
> this:
> XSD_SPECIFIC_TYPE_MAP = new HashMap<String, String>();
> XSD_SPECIFIC_TYPE_MAP.put("string", "String");
> XSD_SPECIFIC_TYPE_MAP.put("decimal", "java.math.BigInteger");
> XSD_SPECIFIC_TYPE_MAP.put("integer", "long");
> If we have a wadl like this:
> <param name="param1" required="true" style="query" type="xs:int" />
> <param name="param2" required="true" style="query" type="xs:long" />
> it's always generate (String param1) and (String param2)
> So far as I know, xs:int and xs:long beside xs:string are the most usage type
> in WADL. But now it can not work any more!!!!
> I think this is a regression bug from
> **********************************************************
> sergeyb 08.05.12 19:25:44
> [CXF-4292] Defaulting to String when WADL Generator can not determine a class
> name of the primitive type
> **********************************************************
> For the solution, I think we can expand XSD_SPECIFIC_TYPE_MAP which the
> exactly mapping as a standard:
> http://en.wikipedia.org/wiki/Java_Architecture_for_XML_Binding
> Could you please have a look on this issue.
> Many many many thanks :)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
