Replying to this old thread. The problem had mysteriously gone away but then
came back just recently. After investigation it turned out that my XSD had
changed and a complexType was no longer supported in the type substitution
hierarchy. However, my test programs were still loading test XML files that
had elements that used the type that no longer existed. The fix was to fix
my test data to not use incorrect types that were no longer supported by
schema. HTH others.
Farrukh Najmi wrote:
>
> am seeing the following exception in my unit tests and am not sure
> what changed to get this exception. Does any one have any ideas? Thanks.
>
> java.lang.NullPointerException
> at
> com.sun.xml.bind.v2.runtime.JAXBContextImpl.getNearestTypeName(JAXBContextImpl.java:663)
> at
> com.sun.xml.bind.v2.runtime.unmarshaller.XsiTypeLoader.parseXsiType(XsiTypeLoader.java:107)
> at
>
--
View this message in context: http://old.nabble.com/NPE-at-com.sun.xml.bind.v2.runtime.JAXBContextImpl.getNearestTypeName%28JAXBContextImpl.java%3A663%29-tp28985639p29738228.html
Sent from the java.net - jaxb users mailing list archive at Nabble.com.