-- xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx
Guy Rouillier wrote:
In jboss-3.2.1\server\default\conf\jboss-service.xml, I set <attribute name="VerifyDeployments">false</attribute>
The others were already set as you describe. Deployment still fails, same class not found error.
Additional factoid: As I already mentioned, if I copy our JAR that contains our exceptions into server\default\lib, everything deploys and runs fine. What I may have failed to mention is that we have another of our JARs in the classpath I specify in my SAR jboss-service.xml, and the EJB *is* able to locate that at runtime. So the EJB definitely must be using the classpath I specify with the SAR (which makes sense now that I think about it - I did verify with Debug that the EJB uses the same classloader as the MBean.) This appears to be purely a deployment time problem.
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
