This is absolutely essential for my project, since I've been seeing the NPE as well but have to produce a product that can deploy under WL 6.1 and JB 3.0. I'm in the midst of porting to JB 3.0 with an application from WL 6.1 and its been quite painful with the various snafus in the beta 1, beta 2, and (presumably) RC1.
Is there any way around this coming up, without having to construct multiple EAR files for various vendors (yuck!)? Or, is this the intended functionality for JB 3.0 now? James > -----Original Message----- > From: David Ward [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 16, 2002 6:38 PM > To: Dennis Muhlestein > Cc: Scott M Stark; [EMAIL PROTECTED] > Subject: Re: [JBoss-user] tomcat 4 issue > > > I had a similar problem when I went from JBoss-2.4.x_Tomcat-3.2.x to > jboss-3.0.0RC1_tomcat-4.0.3. I got in the habit of including my ejb > home and remote interfaces in my war file, which works fine > in the older > version. However, in this latest version, I needed to *not* > include any > ejb interfaces in my war file. Once I took them out, JBoss was happy > (my null pointer like yours went away). I attributed it to the new > "UnifiedClassLoader." I'm not sure if other app servers will > be happy > with this, though. I always try to make my ear's app-server > agnostic. > I have no problem including multiple extra xml descriptors as > they are > just ignored in other servers (ie: jboss-web.xml vs. weblogic.xml), > however which classes have to get included in the ejb-jars or > wars have > to be the same... > > David > > -- > > Dennis Muhlestein wrote: > > > That makes sense, thanks. > > > > When I deploy my own app, I get the same error that I used to get > > before this whole think came about. > > > > CONTAINER EXCEPTION: > > java.lang.NullPointerException > > at > > > org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.i > nvokeHome(StatelessSessionContainer.java:598) > > at > > > org.jboss.resource.connectionmanager.CachedConnectionIntercept > or.invokeHome(CachedConnectionInterceptor.java:167) > > at > > > org.jboss.ejb.plugins.TxInterceptorBMT.invokeHome(TxIntercepto > rBMT.java:54) > > at > > > org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invo > keHome(StatelessSessionInstanceInterceptor.java:57) > > at > > > org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityI > nterceptor.java:104) > > at > > > org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor > .java:109) > > at > > > org.jboss.ejb.StatelessSessionContainer.invokeHome(StatelessSe > ssionContainer.java:300) > > at org.jboss.ejb.Container.invoke(Container.java:727) > > > > Still a ClassLoading problem?? A configuration problem? I wish > > someone could point me in the write path. MyApp is configured > > according to the contents listed below. Tomcat works fine, > EJB works > > fine, I just can't talk from a servlet to an EJB else the > error above. > > > > Thanks > > Dennis > > > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/j> boss-user > _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
