JAXB Reference Implementation Bug ?

S

Sony Antony

I was looking at the code generated by a JAXB compile ( xjc.sh that
came with Java web services package version 1.2 )

( impl.runtime.validatorImpl class )

The code for validateRoot() finally executes this exception handler

-------------------------------------------------------------------
} catch( SAXException e ) {
// TODO exception handling.
// we need a consistent mechanism to convert SAXException
into JAXBException
Exception nested = e.getException();
if( e != null ) {
throw new ValidationException( nested );
} else {
throw new ValidationException( e );
}
//return false;
}

---------------------------------------------------------------------------

I think they meant "if( nested != null )".


This results in a ValidationException being thrown without any useful
information at all contained within, if nested happens to be null.
In otherwords if there is no nested exception original SAXException -
which probably contained a message and definitely stacktrace - is just
thrown away.

1. Am I write in my conclusion above ? Is this a known bug ?

2. What is the best JAXB implementation available out there ?
3. Is the RI known for its standard compliance ?

Thanks
--sony
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,768
Messages
2,569,574
Members
45,050
Latest member
AngelS122

Latest Threads

Top