jboss 3.0 beta

[crismally]

Concerning this version, unfortunately not only the documentation is missing is missing too a lot of correct functionality, I mean is full of bugs like an old cake, I'm sorry! For example if you expect to see your jdbc drivers taken from ../lib/ext/ xxx.jar you can forget about this, you should copy them in whoops ! the .../deploy directory and, as a plus, I didn't succeeded till now to create a very dummy entity bean in the alpha version, server crashes when is calling org.jboss.ejb.plugins.cmp.jdbc.entityExists( Object pk ) it seems that this method receives a null value. In beta even at deployment time a dummy
" org.jboss.deployment.DeploymentException: Could not deploy file:/dummyejb.jar; - nested throwable is: javax.management.MBeanException: Exception in service lifecyle operation: create
at org.jboss.ejb.EJBDeployer.deploy(EJBDeployer.java:475)" will kill your day and nerve ! By the way whats this ' service lifecyle ...' ;-) ?Regards,

[terry_ray]

I'm not sure where the "beta" build is coming from. I'm using a 3.0 build taken from a CVS snapshot on 1/15. I am putting my JDBC drivers in lib/ext and having no problems locating them. One thing I'll mention is that if you're using the alpha build from Nov 01, just putting the JAR in lib/ext won't help. You'll have to explicitly add the file to the classpath archives in conf/default/jboss-service.xml. Or, you could add it to the classpath of the server manually. I noticed in the 1/15 snapshot, that the classpath archive entry in jboss-service.xml picks up everything in lib/ext, so that should take care of that issue.

I haven't tried using CMP in 3.0, so I can't speak to that. But, overall I've been very happy with 3.0, even the early alpha.

[pajama]

Read this, regarding the location of JDBC drivers:
http://main.jboss.org/thread.jsp?forum=46&thread=9762

[davidjencks]

Well I guess one good thing came out of this confused diatribe... I've removed the obsolete classpath elements from the ConnectionFactoryLoader config examples.