jaxb-api
jaxb-api copied to clipboard
xjc can't handle the restriction complext type
Hi,
We are Celtix team[1], and we are using JAXB 2.0 EA3. But with the attached testcase, we have the following errors throwed from JAXB RI.
[java] Parsing schema error: [java] org.xml.sax.SAXParseException: Base complex type "RestrictedCard" is derived by restriction, while this complex type " ard" is derived by extension. This is not currently handled by XJC, but we are seeking input on this issue. Please report this to the JAXB team. [java] Error : An rpc-literal binding in a DESCRIPTION MUST refer, in its soapbind:body element(s), only to wsdl:part element s) that have been defined using the type attribute.
[java] An rpc-literal binding in a DESCRIPTION MUST refer, in its soapbind:body element(s), only to wsdl:part element(s) that have been defined using the type attribute.
Any help will be appreciate.
[1] http://celtix.objectweb.org/
Thanks, James.
Environment
Operating System: All Platform: All
Affected Versions
[2.0 EA1]
- Issue Imported From: https://github.com/javaee/jaxb-v2/issues/149
- Original Issue Raised By:@glassfishrobot
- Original Issue Assigned To: @glassfishrobot
@glassfishrobot Commented Reported by [email protected]
@glassfishrobot Commented [email protected] said: Created an attachment (id=91) test case which have problem
@glassfishrobot Commented kohsuke said: The underlying problem is that this schema types in the following way:
typeX (a,b,c,d) -> typeY by-restriction (a,d) -> typeZ by-extension (a,d,c')
where c is
<xs:element name="PhysicalPort" type="SIDBusRe:PhysicalPort" ... />
and c' is
<xs:element name="PhysicalPort" type="vodTs:Port" ... />
So this can't be just bound like what the spec says, which will produce things in a wrong order (a,c',d) with unnecessary @xsi:type
Hmm...
@glassfishrobot Commented kohsuke said: This requires a spec level attention and thus can't be fixed in 2.1.
@glassfishrobot Commented File: broken.zip Attached By: [email protected]
@glassfishrobot Commented Was assigned to snajper
@glassfishrobot Commented This issue was imported from java.net JIRA JAXB-149