Hi Ed,
The problem does still exist when I pass in the classloader to
JAXBContext.newInstance(packageList, classloader).
I don't think the problem is specific to maven... I think its more of a
Junit issue. Here is the previous thread that discusses the Junit
classloaders.
https://jaxb.dev.java.net/servlets/ReadMsg?listName=users&msgNo=4637
On 12/20/05 5:01 PM, "Ed Mooney" <Ed.Mooney_at_Sun.COM> wrote:
> 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
>>
>>
> [ ... ]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
> For additional commands, e-mail: users-help_at_jaxb.dev.java.net
>
>