Hello,
> I'm encountering some classloader problems when trying to run a junit test
> which calls the Castor marshaller.
> Here are the combinations that I have tried and their effect...
.
> Has anyone been able to run a junit test which uses castor?
I don't know if this is really the same problem as you reported.
But there are really problems using the JUnit GUI together with Castor.
The JUnit GUI runner per default tries to reload all java classes after
each test case. This conflicts with some static object references,
which point to the old classes of the last test case, and results in
some ugly exceptions occuring after the first test run. To overcome
this problem, you can configure JUnit to not reload the Castor (and
maybe also some of your own classes) by inserting additional
exclude entries in the properties file "excluded.properties", for example:
excluded.10=org.exolab.*
You can find and edit this properties file in the junit JAR archive,
at the path junit/runner/excluded.properties.
Regards,
Martin
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-user
