Eclipse Community Forums: EclipseLink » EclipseLink Moxy Dynamic JAXB strange behavior for standard XSD restrictions

Home » Eclipse Projects » EclipseLink » EclipseLink Moxy Dynamic JAXB strange behavior for standard XSD restrictions(Moxy support for standard XSD restrictions)

Show: Today's Messages :: Show Polls :: Message Navigator

EclipseLink Moxy Dynamic JAXB strange behavior for standard XSD restrictions [message #1730670]

Wed, 27 April 2016 14:26

Ruslan Zenin

Messages: 1
Registered: April 2016

Junior Member

Hello,

I'm trying to make EclipseLink Moxy Dynamic entity work with XSD restrictions (EclipseLink version 2.5.2). Lets say I want to restrict usage of some elements from my "base" type. e.g.

<xs:complexType name="PersonName">
        <xs:sequence>
            <xs:element name="FirstName" type="xs:string" minOccurs="0" />
            <xs:element name="LastName" type="xs:string" minOccurs="0" />
            <xs:element name="MiddleName" type="xs:string" minOccurs="0" />
            <xs:element name="AliasName" type="xs:string" minOccurs="0" />
        </xs:sequence>
</xs:complexType>
...
<xs:restriction base="PersonName">
  <xs:sequence>
    <xs:element name="AliasName" type="xs:string" minOccurs="0" />
  </xs:sequence>
</xs:restriction>

How can I generate a valid XML with MOXy? I tried static and dymamic MOXy beans/entities with no luck.

In more details I demonstrate this issue (with all the code) here:
http://stackoverflow.com/questions/36780294/eclipselink-moxy-dynamic-jaxb-strange-behavior-for-standard-xsd-restrictions

[Updated on: Thu, 19 May 2016 14:22]

Report message to a moderator

Previous Topic:	IndirectList executes a contains() check on add(). Why?
Next Topic:	Uni-directional OneToMany problems with JPA2.0 -> JPA2.1 migration

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Mon May 06 15:53:24 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter