Hi Bill,
I don't have any experience with maven, but I'm wondering if you still
have this problem after passing in the application classloader to
JAXBContext.newInstance()?
-- Ed
William Simons wrote:
> Hi Ed,
>
> I was trying to trim down my application to send you a war file and ran
> across some interesting behavior that might shed some light on the
> situation. It appears that the environment that is behaving differently
> than all the rest isn't Tomcat or Jetty but actually Junit within maven (I
> haven't run Junit outside of maven to isolate it). I know that awhile back,
> JAXB2 wasn't working properly within Junit because of a classloader
> conflict. This was corrected but perhaps there are some lingering issues.
>
> I'll continue to investigate but any insight that you have would be helpful.
>
> I'll also come up with some simple example files that work in one
> environment but not the other.
>
>
> Thanks,
> Bill
>
>
[ ... ]