Marcus, I'm afraid most of my attention is focussed on Jetty4 at the moment, although I hope to get back to JBoss3 soon.
The problem boils down to limitations in how Jasper gets hold of it's classpath. There is a properties file somewhere (temporary hack) that should allow you to work around this, or perhaps you could set your classpath explicitly in your MANIFEST.MF. This should all be sorted when Jetty4/JSP1.2 is working in a few weeks, then things should really start moving. Jules --- Marcus Brito <[EMAIL PROTECTED]> wrote: > Hello, folks. > > I've been using JBoss 3.0 for a few days, > experimenting the new CMP 2.0 > stuff. It seems to work fine, congratulations. > > However, I've got some problem deploying a few JSP > files that uses my > beans. Jetty spits a compilation error, complaining > about classes it > could not find: my bean classes. > > So, JBoss isn't setting Jetty classpath to include > my deployed beans, I > think. Has it been fixed in recent builds, it is a > known bug? I'm using > JBoss 3.0 checked out from CVS about a week ago. > > -- > Ja ne, > Pazu > mailto: [EMAIL PROTECTED] > > Anime Gaiden: de f�s para f�s, sempre. > > ATTACHMENT part 2 application/pgp-signature __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
