Hi!
Terry Child wrote:
> I've cross posted the following to the castor mailing list and was recommended to
>put my beans.jar in the \jboss\lib\ext
> directory as well as in \jboss\deploy because castor and jboss use different class
>loaders - seems a bit inelegant.
> Is this really the only solution?
>
> --------------------------------
>
> I've tried using JDO within jBoss session beans i.e. I've packaged my beans and
>value objects
> into a beans.jar and put them in the \jboss\deploy directory and I've put the needed
>castor jars into \jboss\lib\ext so they can be
> seen from within jboss. Unfortunately I get the following exception unless I put my
>beans.jar file in the \jBoss\lib\ext
> directory also:
<snip>
This is due to a bug in Castor. Libraries such as Castor need to take
into consideration the context in which they are used. When it comes to
classloading they must use the classloader provided by
Thread.getContextClassLoader(), and load classes from there.
When this is fixed in Castor you should be able to add Castor to jBoss'
lib/ext, and not include it with your beans. When you use Castor from
within your beans, Castor should then be able to access your classes
which are loaded by the EJB classloader, which is set as the context
classloader.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
