Does anyone has experience of taking= =20an Axis2 AXIOM OMElement and unmarshalling this into a JAXB generated object= ?

If so could you please explain= =20how to do this. I have managed to take a JAXB object and convert this to a OM= Element but can't seem to get this to work the other way.

Any help would be appreciated.<= /o:p>

Regards Tanya

Tanya Beech
Signal Processing

QinetiQ
Bldg E Rm 103
Malvern Technology Centre
St. Andrews Road, Malvern
Worcestershire, WR14 3PS

= =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20

=20 Tel: =20	=20 01684 895232 =20
=20 Email: <= /p> =20	=20 tbeech@QinetiQ.com =20
=20 Mobile: = =20	=20 07766 134364 =20
=20 Web: =20	=20 QinetiQ - The Global Defence and Security Experts From: Ian Carr [mailto:ian.carr@focus-solutions.co.uk] Sent: 22 March 2006 15:59<= br> To: users@jaxb.dev.java.ne= t Subject: Optional List bas= ed attributes and marshalling I have a query about the way JAXB is marshalling an op= tional list based attribute. My schema contains an optional attribute of type xs:ID= REFS, using the EA3 build of JAXB 2 (jaxb-ri-20051223) I get the generated clas= ses I would expect with this attribute being given an accessor with the followi= ng signature: public List<Object> getTwo() {= if (two =3D=3D null) {<= /o:p> two =3D n= ew ArrayList<Object>(); } return this.two;<= /span> } If I create and marshal an instance of the class it pr= oduces the expected output: <X/> However if the accessor is invoked before marshalling = it produces the following output, with an empty 'two' attribute:<= /span> <X two=3D""/> This isn't a major issue, but one of my validators the= n complains that the empty IDREFS attribute is not legal. Looking at the XM= L schema spec it says: "The value space<= /a> of IDREFS is the set of finite, non-zero-length sequences of IDREFs"<= /span> Which if I am reading it correctly means that a zero-l= ength or "" value is incorrect. Is there something I am not doing in my schema, custom= binding script or code that would suppress this empty attribute? Ian Carr The information contained in this E-Mail a= nd any=20 subsequent correspondence is private and is intended solely for the=20 intended recipient(s). The information in this communication may= =20be=20 confidential and/or legally privileged. Nothing in this e-mail i= s=20 intended to conclude a contract on behalf of QinetiQ or make QinetiQ s= ubject=20 to any other legally binding commitments, unless the e-mail contains a= n=20 express statement to the contrary or incorporates a formal Purchase=20 Order. For those other than the recipient any dis= closure,=20 copying, distribution, or any action taken or omitted to be taken in r= eliance=20 on such information is prohibited and may be unlawful. Emails and other electronic communication = with=20 QinetiQ may be monitored and recorded for business purposes including = security, audit and archival purposes. Any response to this emai= l=20 indicates consent to this. Telephone calls to QinetiQ may be monitore= d or=20 recorded for quality control, security and other business=20 purposes. ------_=_NextPart_001_01C64DCB.13100B5A--