Hi,
this should not happen in the normal out-of-the-box setup. Maybe you
are using some special XML parser or JAXB implementation that does not
resolve these references?

Regard, aki

On Thu, Feb 24, 2011 at 7:59 PM, Tim Clotworthy
<[email protected]> wrote:
> ello,
>
> I am getting unmarshalling exceptions at any encounter of sequences &lt; and 
> &gt; in my xml. I tried wrappering the corresponding pieces with CDATA like 
> <![CDATA[&gt;]]>, but the exception still occurs.
>
> I am using the following classes for performing the unmarshalling activities:
>
> import javax.xml.bind.JAXBContext;
> import javax.xml.bind.JAXBException;
> import javax.xml.bind.Unmarshaller;
> import javax.xml.transform.Source;
> import javax.xml.transform.stream.StreamSource;
>
> and the exception takes place in the "f = (Filter) u.unmarshal(s);" part of 
> the code below:
>
> JAXBContext jbc = null;
> Unmarshaller u = null;
> Filter f = null;
> try {
> jbc = JAXBContext.newInstance(Filter.class);
> } catch (JAXBException e) {
> // TODO Auto-generated catch block
> e.printStackTrace();
> }
> try {
> u = jbc.createUnmarshaller();
> } catch (JAXBException e) {
> // TODO Auto-generated catch block
> e.printStackTrace();
> }
> StringReader sr_xml = new StringReader(filter);
> Source s = new StreamSource(sr_xml);
> try {
> f = (Filter) u.unmarshal(s);
> } catch (JAXBException e) {
> // TODO Auto-generated catch block
> e.printStackTrace();
> }
>
> I would be grateful for any insights into how to resolve this. thank you for 
> any response!
>

Reply via email to