Hi!
Sebastien Alborini wrote:
> > I placed the archive (parser.jar) which contains those
> > classes in the lib/ext directory (maybe that's wrong
> > from the beginning) and jBoss adds the archive to the
> > classpath at startup (or looks like).
>
> This is wrong. Jboss and your beans won't share the same classloader, so
> it's no use giving the jar to jboss.
>
> Your beans can only access the classes which are in the
> <jboss>/deploy/your_app.jar file. You must put all you need in here.
WHOA! Stop right there! Sorry, but this is wrong. Classloader
delegation. The classloader used to load the EJB's use the server
classloader as parent, so EJB's can indeed use any class in /lib/ext.
Furthermore, any libraries that do EJB-restricted operations, such as
reading files and creating threads, MUST be in /lib/ext (or whereever,
just not in the EJB-jar). Fransisco is doing this absolutely correct.
The problem is something else. Do you have the possibility of putting a
try/catch(e.printStackTrace) around the operation that fails? That
should give more info on what goes wrong.
/Rickard
--
Rickard �berg
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]
