> What I'm seeing now is, if I deploy my sar (which has > all my classes, > including the EJB implementation classes).
The SAR classes will see EJB ones from the SAR. do you have the *implementation* class in there as well? if so remove that. Then > deploy my EAR file. > > Subsequent re-deployes of the EAR, look as though > they are re-deploying, > but when I access the EJBs, they are using the old > classes (from the SAR > I assume). That is normal, you packaged static classes in the SAR. When you deploy an ear, since we still use the delegation model from 2.x. the CL for the EJB has SAR CL has parent and sees the classes in the SAR. BTW 3.x will do away with this delegate app-service. Don't package the implementation classes with the SAR marcf > The SAR isn't changing, just the EJBs in the EAR, so > in effect, I have > multiple versions of the same class under deploy. > It seems as though the CL is finding the SAR copy of > the file, and > ignoring my re-deployment. > > This requires that I restart jboss to see my new EJB > code. > > > Can someone tell me which > descriptor/auto-deployer/hot-deployer I need > to wave a dead chicken over to get it to work? > > Restarting jboss in between little 1 line fixes to my > code seriously > sucks. > > Do I have to remove the EJB code from my SAR to make > this all work? I > have a lot of common code between EJBs and MBeans, so > getting rid of the > EJB files from the SAR is only a little fix. > > I thought this used to work (but I could be wrong on > that one). > > -David > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-dev > lopment ______________________________________________________________________ View: http://jboss.org/forums/thread.jsp?forum=66&thread=5208 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
