there has been a problem with Jasper not finding the standard JSP-jars (servlet.jar) for compilation under Windows systems due to jetty.properties using a platform-dependent format. I have fixed the intepretation of that file a few weeks ago, so I do not know whether a cvs update will help you ...
CGJ -----Ursprüngliche Nachricht----- Von: Marcus Brito [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 9. November 2001 12:33 An: Jboss Mailing List Betreff: [JBoss-user] JBoss 3.0 not setting Jetty classpath 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. _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
