Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: error (athena.apache.org: encountered temporary error during SPF
 processing of domain of hutao722@163.com)
Date: Mon, 16 Sep 2013 02:25:40 -0700 (PDT)
From: hutao722 <hutao722@163.com>
To: users@camel.apache.org
Message-ID: <1379323540820-5739509.post@n5.nabble.com>
In-Reply-To: <F72E7A6DE48A43CA937EB62EF230D489@gmail.com>
References: <1379306406876-5739497.post@n5.nabble.com>
 <F72E7A6DE48A43CA937EB62EF230D489@gmail.com>
Subject: Re: JAXB partial unmarshalling
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Thank you for your explain, Willem. But i read from the link
http://camel.apache.org/jaxb.html
it says: 

JAXB 2 supports marshalling and unmarshalling XML tree fragments. By default
JAXB looks for @XmlRootElement annotation on given class to operate on whole
XML tree. This is useful but not always - sometimes generated code does not
have @XmlRootElement annotation, *sometimes you need unmarshall only part of
tree*.
In that case you can use partial unmarshalling. To enable this behaviours
you need set property partClass. Camel will pass this class to JAXB's
unmarshaler.

i thought the partial unmarshalling can unmarshall the only part of tree.
Now my question is that if i have a big SOAP response and i only wish to
focus on just small pieces, as you said,  i need to travel the xml tree by
dom or sax and skip the unnecessary content, right? This may have a lot of
work to do, do we have better ways?

Thanks!    


--
View this message in context: http://camel.465427.n5.nabble.com/JAXB-partial-unmarshalling-tp5739497p5739509.html
Sent from the Camel - Users mailing list archive at Nabble.com.