JAXB Unmarshalling question

I want to create Java objects from an XML file; JAXB sounds like the way to go, from what I've read.
One question though: the object I want to create is an existing class. What I'd like to do is have JAXB create objects of the existing class, instead of the bean class that the JAXB binding compiler creates from looking at the schema.
Is there a way to do this? Am I using the wrong tool? The existing class does not adhere to the bean standard.
Thanks!

Hi,
You could place the binding schema,xml document,dtd could be at any location on your filesystem.When you use the binding compiler, you need to specify the location.
For ex. you could use as following:
D:\Softwares\jwsdp1.2\jaxb\bin\xjc -b c:\binding.xjb d:\examples\example.xsd
If your are using jwsdp1.3, you need to set the JAVA_HOME and JWSDP_HOME environment variables.
Refer the section "configuring and running the samples" for details at http://java.sun.com/webservices/docs/1.3/tutorial/doc/JAXBUsing2.html#wp87739
-Amol

Similar Messages

JAXB unmarshalling error

We are getting a JAXB unmarshalling error:
while processing the following <condition> tag which is of type xsd:string
<condition> x < 100 </condition>
The error is probably happening due to "<" token as a part of string type.
xml.bind.JAXBException: Unexpected error in Unmarshalling
at oracle.xml.jaxb.JaxbUnmarshaller.unmarshal(JaxbUnmarshaller.java:224)
Any ideas how to resolve this issue?
Note
<condition> x >100 </condition> is getting unmarshalled successfully by JAXB unmarshaller.
Thanks

Hi,
Did you tried to put & lt; (without space) instead of < ?
Best Regards,
Paweł

JAXB unmarshalling error for " " token as part of xsd:string type element

JAXB unmarshalling error for "<" token as part of xsd:string type element
We are getting a JAXB unmarshalling error:
while processing the following <condition> tag which is of type xsd:string
<condition> x < 100 </condition>
The error is probably happening due to "<" token as a part of string type.
xml.bind.JAXBException: Unexpected error in Unmarshalling
at oracle.xml.jaxb.JaxbUnmarshaller.unmarshal(JaxbUnmarshaller.java:224)
Any ideas how to resolve this issue?
Note
<condition> x > 100 </condition> is getting unmarshalled successfully by JAXB unmarshaller.
Thanks

Hi,
Did you tried to put & lt; (without space) instead of < ?
Best Regards,
Paweł

Problem with JAXB Unmarshall - javax.xml.bind.UnmarshalException

Hi,
I'm getting an expection while unmarshalling using JAXB. The error is as follows :
DefaultValidationEventHandler: [ERROR]: unexpected element (uri:"http://www.etrade.com/ee/systemdomainao/search", local:"Context_Id"). Expected elements are <{}contextId>,<{}predicateInterceptor>,<{}isDefaultsearch>,<{}implicitContextSQL>,<{}contextName>,<{}searchId>,<{}implicitContextText>
I've generated JAXB classes using xjc command from my schema. The root element is Search object which has a List of Searchcontext and Columlist object. When I'm trying to unmarshall the XML, I'm getting the above exception. What is baffling, if I comment out the <tns:SearchContext> entry from the XML, unmarshall doesn't throw any exception and populates the columnlist properly. Columnlist and Searchcontext have little difference except that columnlist contains more elements.
Here'e the unmarshall code,
URL metadataURL = this.getClass().getClassLoader().getResource("metadata/search/PARTICIPANT.xml");
JAXBContext jc = JAXBContext.newInstance("com.etrade.ee.systemdomainao.search.domain");
Unmarshaller unmarshaller = jc.createUnmarshaller();
unmarshaller.setEventHandler(new javax.xml.bind.helpers.DefaultValidationEventHandler());
Search search = (Search)unmarshaller.unmarshal(metadataURL);
Any pointers will be highly appreciated.
Thanks

XSD :
XSD :
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://www.etrade.com/ee/systemdomainao/search" targetNamespace="http://www.etrade.com/ee/systemdomainao/search" elementFormDefault="qualified" attributeFormDefault="unqualified">
     
     <xs:complexType name="Searchcontext">
          <xs:sequence>
               <xs:element name="Context_Id" type="xs:int"/>
               <xs:element name="Search_Id" type="xs:string"/>
               <xs:element name="Context_Name" type="xs:string"/>
               <xs:element name="Implicit_Context_SQL" nillable="true">
                    <xs:simpleType>
                         <xs:restriction base="xs:string">
                              <xs:maxLength value="500"/>
                         </xs:restriction>
                    </xs:simpleType>
               </xs:element>
               <xs:element name="Implicit_Context_Text" nillable="true">
                    <xs:simpleType>
                         <xs:restriction base="xs:string">
                              <xs:maxLength value="500"/>
                         </xs:restriction>
                    </xs:simpleType>
               </xs:element>
               <xs:element name="Is_Defaultsearch" type="xs:boolean" nillable="true"/>
               <xs:element name="Predicate_Interceptor" type="xs:string" nillable="true"/>
          </xs:sequence>
     </xs:complexType>
     
     <xs:complexType name="Columnlist">
          <xs:sequence>
               <xs:element name="Columnlist_Id" type="xs:int"/>
               <xs:element name="Search_Id" type="xs:string"/>
               <xs:element name="Is_Quicksearchable" type="xs:boolean" nillable="true"/>
               <xs:element name="Is_Advancesearchable" type="xs:boolean" nillable="true"/>
               <xs:element name="Is_Quicksearchview" type="xs:boolean" nillable="true"/>
               <xs:element name="Is_Fullview" type="xs:boolean" nillable="true"/>
               <xs:element name="Is_Sortable" type="xs:boolean" nillable="true"/>
               <xs:element name="Is_Defaultsort" type="xs:boolean" nillable="true"/>
               <xs:element name="Default_SortOrder" type="xs:string" nillable="true" minOccurs="0"/>
               <xs:element name="Display_Order" type="xs:int" nillable="true"/>
               <xs:element name="Default_Value" type="xs:string" nillable="true" maxOccurs="6"/>
               <xs:element name="Default_Operator" type="xs:string" nillable="true"/>
               <xs:element name="Is_Closedset" type="xs:boolean"/>
               <xs:element name="Closedset_List_Name" type="xs:string" nillable="true"/>
               <xs:element name="Is_RelatedMenu" type="xs:boolean" minOccurs="0"/>
               <xs:element name="Column_Name" type="xs:string"/>
               <xs:element name="Display_Name" type="xs:string"/>
               <xs:element name="Is_UDF" type="xs:boolean" nillable="true"/>
               <xs:element name="Table_Name" type="xs:string"/>
               <xs:element name="Data_Type" type="xs:string"/>
               <xs:element name="Column_Size" type="xs:int"/>
          </xs:sequence>
     </xs:complexType>
     
     <xs:element name="Search">
          
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="Search_Id" type="xs:string"/>
                    <xs:element name="Schema_Set">
                         <xs:simpleType>
                              <xs:restriction base="xs:string">
                                   <xs:maxLength value="20"/>
                                   <xs:minLength value="1"/>
                              </xs:restriction>
                         </xs:simpleType>
                    </xs:element>
                    <xs:element name="SearchContext" type="tns:Searchcontext" maxOccurs="unbounded"/>
                    <xs:element name="ColumnList" type="tns:Columnlist" maxOccurs="unbounded"/>
               </xs:sequence>
          </xs:complexType>
          <xs:key name="Search_PrimaryKey_1">
               <xs:selector xpath="."/>
               <xs:field xpath="tns:Search_Id"/>
          </xs:key>
          <xs:keyref name="Searchcontext_ForeignKey_1" refer="tns:Search_PrimaryKey_1">
               <xs:selector xpath=".//tns:SearchContext"/>
               <xs:field xpath="tns:Search_Id"/>
          </xs:keyref>
          <xs:keyref name="Columnlist_ForeignKey_2" refer="tns:Search_PrimaryKey_1">
               <xs:selector xpath=".//tns:ColumnList"/>
               <xs:field xpath="tns:Search_Id"/>
          </xs:keyref>
          <xs:key name="Searchcontext_PrimaryKey_1">
               <xs:selector xpath=".//tns:SearchContext"/>
               <xs:field xpath="tns:Context_Id"/>
          </xs:key>
          <xs:key name="Columnlist_PrimaryKey_1">
               <xs:selector xpath=".//tns:ColumnList"/>
               <xs:field xpath="tns:Columnlist_Id"/>
          </xs:key>
     </xs:element>
</xs:schema>

JAXB unmarshalling problem

Hi
I have a problem with unmarshalling.
when my XML document is valide ,there is no probem but when the document is not valid(for exemple i put a String value in an element of type xs:decimal) i get a strange result:I thought that i will get a java.lang.NumberFormatException when i set the java attribute mapped with that element or i get the error value but this attribute get null as value and there is no NumberFormatException.

riadhhwajdii wrote:
Is there any way to modify this default behavior for jaxb to make it show the error value or get a java exceptionyes, see [this post|http://forums.sun.com/thread.jspa?messageID=11031834#11031834]
Edited by: jtahlborn on Aug 8, 2010 10:01 AM

JAXB unmarshalling elements with xs:type explicitly set

I am working with XML content where the XSD defines an element as being of a complexType (say "ParentType") but the content explicitly sets the element's xs:type attribute to an extension of that complexType (say "ChildType").
As far as I can tell the XML is valid, but JAXB issues the following when unmarshalling:
DefaultValidationEventHandler: [ERROR]: Unexpected element {}:child1
javax.xml.bind.UnmarshalException: Unexpected element {}:child1
Where <child1> is added via the extension.
Is this a problem with JAXB or my XSD?
(XSD and XML enclosed below)
XSD ------------------
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:complexType name="ParentType">
<xs:sequence>
<xs:element name="parent1" type="xs:string"/>
<xs:element name="parent2" type="xs:string"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="ChildType">
<xs:complexContent>
<xs:extension base="ParentType">
<xs:sequence>
<xs:element name="child1" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="root">
<xs:complexType>
<xs:sequence>
<xs:element name="child" type="ParentType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
XML -----------------------
<?xml version="1.0" encoding="UTF-8"?>
<root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="problem.xsd">
<child xsi:type="ChildType">
<parent1/>
<parent2/>
<child1/>
</child>
</root>

JAXB doesn't handle OO schema design. I tried to do something similar where I defined a type called base and then defined that my document contained 1 or more base elements. Then I tried to unmarshall a document that contained elements that were of types extending from base. I ended up with the same issue.
It seems that when the xjc compiler defines the classes it isn't smart enough to realize the element defined as parent could also contain a child element since child extends parent. Your XSD and XML are valid.
I would think that JAXB should identify that because there is a type the extends the defined type, that an element of the sub-type might be subsituted i.e. check the actual type of the element in the XML before attempting to unmarshall it as the default type. It doesn't do that. I am not sure if this is as desinged, or a flaw in the implementation.

JAXB unmarshalling date

I have used JAXB to marshall a java class for a date information. The resulting XML data looks fine. It contains the date I want. However, once I'm trying to unmarshall the XML file using JAXB I cannot retrieve the date back.
For example, my object contain a startTime field that is java.util.Calendar.
if I'm doing..... object.getStartTime() I would get null in return?
Does anyone encounter this problem before? Or anyone know a solution to this? Any pointer would be highly appreciated.

To give you more information.....
i have debugged more into this.
My code is able to retrieve the date string back from the XML data which is:
2006-02-01-08:00
This string is in a variable "lexval"
However, this following statement return null value:
oracle.xml.jaxb.JaxbDatatypeConverter.parseDate(lexval)
Anybody has any idea on this issue? does parseDate method has any restriction?
--Thanks

Jaxb unmarshalling and setvalidating()

I am using jaxb 1.0 with jdk1.4 , i am trying to unmarshall the incoming request which a xml.
It has a element called attachment list which is mandatory as per the schema. but i dont want my unmarshaller to validate request and throw error instead i just need to objects from unmarshaller. so i set the setvalidating(false).but i am still getting the validation error.Any help in this is highly appreciated.

Check the date of the post dude - its months old and the dude who posted it hasn't been back since then (only one post, this one). If you want to help, focus on recent threads. Resurrecting old threads triggers other helpful people to unnecessarily invest time into them and creates extra work for the moderators.

Jaxb unmarshalling: how to ignore unknown elements?

Hi,
I use jaxb 1.1 for communication with an external partner. (Took schema, compiled it, used generated classes for unmarshalling like this:
Document doc = /* some document building */
JAXBContext jaxbContext = JAXBContext.newInstance(MyConstants.JAXB_PACKAGE);
Unmarshaller unMarshaller = jaxbContext.createUnmarshaller();
myObject = (MyObject) unMarshaller.unmarshal(doc);) Everything worked fine until they decided to add new elements to their xml-Document without notifiing me (nothing very unusual I think...). Now I get a javax.xml.bind.UnmarshallingException with Message "Unexpected Element". Is there any way to ignore such elements and just take the known Elements from the xml-stream?
Thanks in advance
Thomas

Update your schema with the following after you known elements.
<xs:any namespace="##any" processContents="skip" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>An extension point for arbitrary xml value fragments</xs:documentation>
</xs:annotation>
</xs:any>
Hunter

JAXB Unmarshalling complexity

Hello all,
I need help on JAXB
the situation is as below...
i have to write a program that communicates with a server. the communication is request-response kind of communication which is to be carried out through XML.
so everytime i have to send any request i need to create an XML and then send it to the server. i get the response in the form of XML. then i have to parse the XML to find out whats the response.
previously i used DOM and SAX for creating XML and parsing XML respectively.
now every response i get, i have to validate it against a DTD.
now i'm trying out JAXB. so i first converted all the DTDs to XSD (xml schema docs). because JAXB doesn't support DTDs.
now with JAXB, i'm creating the XML requests and sending it to the server and getting the response.
but here is one problem.....
as with JAXB, of i have to unmarshall the xml response i have to first create a JAXB context. and unmarshall it to that xml object that i'm expecting. but suppose i get some other response then how am i supposed to know that.
i'll explain the above with a small example.
suppose i have the following DTDs
SearchRequest.dtd..............for search requests
SearchResponse.dtd..............for search responses
ErrorResponse.dtd.............for if the server sends any error.
now first i convert this DTDs to XSDs and so i get
SearchRequest.xsd, SearchResponse.xsd, ErrorResponse.xsd
and then using the JAXB compiler i create the JAXB derived classes in the following package
com.xyz.SearchRequest
com.xyz.SearchResponse
com.xyz.ErrorResponse
now suppose i created the xml request and sent it to the server and i got the response. and i have to unmarshall it.
(the server will send me SearchResponse.xml if everything if fine but ErrorResponse.xml it theres an error).
now heres the problem. the server will send the SearchResponse or ErrorResponse. and ill have to determine what it is before i start to unmarshall.
i hope i have communicated my problem....
thankyou
java-jones

Not sure if this will help you or if this is what you are looking for, but from the JAXB Users' Guide:
More About Unmarshalling
The Unmarshaller class in the javax.xml.bind package provides the client application the ability to convert XML data into a tree of Java content objects. The unmarshal method for a schema (within a namespace) allows for any global XML element declared in the schema to be unmarshalled as the root of an instance document. The JAXBContext object allows the merging of global elements across a set of schemas (listed in the contextPath). Since each schema in the schema set can belong to distinct namespaces, the unification of schemas to an unmarshalling context should be namespace-independent. This means that a client application is able to unmarshal XML documents that are instances of any of the schemas listed in the contextPath; for example:
JAXBContext jc = JAXBContext.newInstance( "com.acme.foo:com.acme.bar" );
Unmarshaller u = jc.createUnmarshaller();
FooObject fooObj = (FooObject)u.unmarshal( new File( "foo.xml" ) ); // ok
BarObject barObj = (BarObject)u.unmarshal( new File( "bar.xml" ) ); // ok
BazObject bazObj = (BazObject)u.unmarshal( new File( "baz.xml" ) ); // error

JAXB Related Question

Hi All,
I have started working on JAXB 1.4 reference implementation provided by sun. I have following questions.
1. Do we have any implementation which simply has the Jar files which can be placed in the classpath and can be used. Right now this reference implementation from sun has lot other things also.
2. I have bee able to use JAXB 1.4 with JDK1.3.1_08 ad as far as what I am tryig to do it looks fine. Are there any issue's with JDK 1.3.1 because I have see somewhere in the documentation it recommends JDK 1.4.
Thanks,
Alok

If you're planning to redistribute JAXB, the license requires you to include a subset of the libraries:
https://jaxb.dev.java.net/faq/index.html#runtime_jars
http://java.sun.com/webservices/docs/1.4/ReleaseNotes.html#RedistributableComponents
Otherwise, just make sure the libraries in that list are in your CLASSPATH. $JWSDP_HOME/jaxb/bin/xjc.bat does that for you. Or, you can run jaxb-xjc.jar:
http://java.sun.com/webservices/docs/1.4/jaxb/xjc.html
You should be fine on 1.3.1_b08, but we did all our JDK 1.3 testing on 1.3.1_10-b03.
-- Ed

JAXB class question

does anyone know which jar file has the javax.xml.XMLConstants class? I'm getting an error while going through some examples for JAXB and I am almost positive that my classpath is messed up or not pointing to the right jars.

Good job mate. That's the way!
And you came back and let us know we needn't waste precious time answering a solved question. That's just exellent. Thanks.
:)

JAXB Unmarshalling and namespace

Hi All ,
Im using jaxb to marshall and unmarshall xml messages.Every thing seems to work fine expect for one
small part ...... the namespace is removed form the xml .For example
<RECORD xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="Record.xsd">
becomes
<RECORD>
Any idea why this happens ?
thanks
Jim

Hi Jimmy -
Have you tried including this code at marshall time?
marshaller.setProperty( Marshaller.JAXB_SCHEMA_LOCATION, "schema_path path_to_xsd.xsd");
Good luck.
cm

JAXB Unmarshall Validation Error Handling

Hello,
During unmarshalling, if say a required element is missing, a ValidationEvent is created and passed to the handleEvent(ValidationEvent e) method of a custom class implementing the ValidationEventHandler interface.
From the ValidationEvent, one can get the ValidationEventLocator, which allows you to find out the column and row numbers of where the validation failed in the XML file.
The problem is, this XML file that is being unmarshalled/marshalled is hidden from the user and not allowed to be accessed directly. I would like to tell the user where the validation failed by referencing nodes instead of column/line numbers.
For example, if an element called 'foo' requires one child 'bar', and if 'bar' is discovered as missing during unmarshalling, the message that comes with the ValidationEvent will say:
uncompleted content model. expecting: <bar>
I don't see a way to find out exactly where in the entire XML file that 'bar' is supposed to occure. How do I find out that the 'bar' element is expected to be under 'foo' element?
Using the Eclipse debugger, I can see that the parent 'foo' is referenced somewhere deep within the JAXB impl classes, but I don't see any public methods that will allow me to get it.
Any ideas?
Thanks,
AJ

Try 'ValidationEventLocation.getObject()', and see if you can narrow it down from there.
I'm also looking for a better solution, since I have a case where a child element is violating it's pattern restrictions, but all I get is a reference to the parent, with no apparent indication as to which child is at fault.

JAXB unmarshalling

Hi,
I'm using JAXB 1.0-ea on W2K Server and have noticed that when I first unmarshal a 1KB file it takes 800ms. I then immediately unmarshall a 26KB file and it takes 400ms.
I'm wondering if somebody has any ideas as to why the 1KB file is taking twice as long to unmarshall as the 26KB file?
thanks,
Dean

I have 2 XML files, file A is 1KB and file B is 26KB. File A is exactly the same structure as file B with no difference in complexity or depth of the XML structures, its only shorter.
When I load these 2 files in a loop the timings I get are kinda interesting, as this is what I see:
File A: 590ms
File B: 340ms
File A: 16ms
File B: 110ms
File A: 0ms
File B: 80ms
File A: 0ms
File B: 31ms
File A: 0ms
File B: 125ms
File A: 0ms
File B: 220ms
The above timings are for the unmarshalling of the XML file, eg MyRootElement.unmarshal(fileInputStream);
So, does anybody have any ideas why loading file A is taking so long on the first load, and nothing on subsequent loads? I'm using JAXB 1.0-ea on W2K using JDK1.4.1.
thanks,
Dean

JAXB Unmarshalling question

Similar Messages

Maybe you are looking for