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-1235) Suggestion: use @WebParam cues when auto-generating request wrappers for Doc/Lit/Wrapped
Date Wed, 28 Oct 2009 17:59:59 GMT

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

Daniel Kulp resolved CXF-1235.
------------------------------

       Resolution: Won't Fix
    Fix Version/s: Invalid


With 2.2.x, the resulting wsdl is pretty different, but still invalid,but it's in JAXB's hands.
  We basically, map the params into wrapper beans and let jaxb generate the schema for everything.
  Now it generates:
<xs:element form="qualified" minOccurs="0" name="bean1" type="testBean1"/>
<xs:element form="qualified" maxOccurs="unbounded" minOccurs="0" name="beanArray" nillable="true"
type="testBean1"/>

so the names are correct, but there isn't a type for testBean1 as testBean1 is an element
with an anonymous type.

The GOOD news is that the code generators and such then complain that the schema complains
missing types.  The javascript stuff complains about missing type, etc....




> Suggestion: use @WebParam cues when auto-generating request wrappers for Doc/Lit/Wrapped
> ----------------------------------------------------------------------------------------
>
>                 Key: CXF-1235
>                 URL: https://issues.apache.org/jira/browse/CXF-1235
>             Project: CXF
>          Issue Type: Improvement
>          Components: JAX-WS Runtime
>    Affects Versions: 2.1
>            Reporter: Benson Margulies
>            Assignee: Daniel Kulp
>             Fix For: Invalid
>
>
> Open up org.apache.cxf.javascript.fortest.SimpleDocLitWrapped, and comtemplate 'beanFunction'.

> It takes two parameters: one of type TestBean1, and one of type TestBean1[].
> TestBean1 has an XmlRootElement annotation.
> RFSB and JAXB build out the unwrapped parts and the schema by using the XmlRootElement
and ignore the @WebParams on the params. The result is a schema with a sequence of two <element
ref='ns:testBean1'/> (one of the two has maxOccurs set for the array).  Thus, two elements/parts
with the same name, which is not a good thing, and the whole idea of the WebParam(name="x")
is to allow the coder to avoid it. The suggestion is to suppress the isElement=true in this
case, and just build a complexType that has two local elements with the names from the WebParams
in them.

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


Mime
View raw message