You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2011/07/21 00:29:57 UTC

[jira] [Resolved] (CXF-3664) wadl2java : xsd data types aren't mapped to java data types properly if they use mixed case.

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

Sergey Beryozkin resolved CXF-3664.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.5
                   2.4.2
         Assignee: Sergey Beryozkin

thanks for this example - I missed yesterday that it were the type names which were used with non-anonymous complex types.

Thus JAXBElementProvider with marshalAsJAxbElement property needs to be configured in such cases - however I think we may just need to add an option like -config (where Spring/etc config would be generated with providers added) or update the main code - to be generated as well 

> wadl2java : xsd data types aren't mapped to java data types properly if they use mixed case.
> --------------------------------------------------------------------------------------------
>
>                 Key: CXF-3664
>                 URL: https://issues.apache.org/jira/browse/CXF-3664
>             Project: CXF
>          Issue Type: Bug
>          Components: Tooling
>    Affects Versions: 2.4.1
>         Environment: Windows 7 32 bit
> java version "1.6.0_26"
> Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
> Java HotSpot(TM) Client VM (build 20.1-b02, mixed mode, sharing)
>            Reporter: Ceri Hughes
>            Assignee: Sergey Beryozkin
>             Fix For: 2.4.2, 2.5
>
>         Attachments: example.zip
>
>
> The data types in my xsd use mixed case names - e.g. "userDefaults"
> When I reference these in my reponse's representation elements, the wadl2java tool is unable to match them to the types processed by the xsd parser.
> E.g.
> <response status="200">
>     <representation mediaType="application/xml" element="fmc:userDefaults" />
> </response>
> There is a line of code in the org.apache.cxf.jaxrs.ext.codegen.SourceGenerator.matchClassName method that checks the lower-cased version of the generated class name matches the local name of the type from the xsd. This will only ever work ig the local name is completely lowercased OR the method changes to match the 2 strings lower cased.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira