This is the simplified scenario:
Using JAXB code the first line below will fail on some of the objects I'm using:
context = JAXBContext.newInstance( MyClass.class );
Unmarshaller unmarshaller = context.createUnmarshaller();
StringReader rdr = new StringReader( input );
Object obj = unmarshaller.unmarshal( rdr );
When I run the code using a simple command line java program using 1.6 java w/ no special classpath the code works but when I copy
the code into a weblogic ear project, the same exact code fails. Well, it fails under windows but seems to run ok under the linux cluster.
The exception I get is:
<exception code="UNKNOWN">com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of IllegalAnnotationExceptions
If a class has @XmlElement property, it cannot have @XmlValue property.
So, I'm guessing jrocket JAXB is running things a little more strict than plain old java under windows? Is there anyway to
get weblogic to use the plain java JAXB path through the code? Maybe a classpath setting will fix this?
Also, I'm still pretty new to weblogic and I was tying to repro the scenario outside of weblogic but haven't been successful. Is it
possible to run a simple java program (.class files only) under the weblogic VM/class loaders w/out starting up the server?
Edited by: 928602 on May 11, 2012 7:59 AM