Hi, good news It seems that I solved this problem ...
So it appears that the problem is coming from an infamous classnotfound error hidden by this ORB init failure exception. At least in the version 3, you must do exactly the contrary than : > What if you move your jar to the JBoss lib/ext > directory instead of having it in your classpath? > I guess that should get you around security > restrictions. > So I have to add explicitely the jacorb.jar in the classpath. Moreover, it seems that the verifyer now verify that the class needed to deploy your ejb is part of the deployer file itself : I use to have a large set of classes not under intensive development stored in a jar accessible from the classpath, while the deployement of a subset of them, was done in another jar together with the class under intensive development. The deployer (3.0a) is now failing in deploying the small jar (if I include them it is ok) I also tried to put them (and the jacorb.jar) in a library folder of an ear file but it is failing too. I may have done something wrong but It may be a bug in 3.0 ? Anyway, thanks for the help of everybody and to the developpers of these great open source projects tha are JacOrb and JBoss. jc > > _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
