Bugs item #548668, was opened at 2002-04-25 08:41
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=548668&group_id=22866

Category: CatalinaBundle
Group: CVS HEAD
>Status: Pending
>Resolution: Accepted
Priority: 7
Submitted By: David Ward (dward2)
Assigned to: Scott M Stark (starksm)
Summary: 3RC1-catalina invokeHome/classload prob

Initial Comment:
Operating System:
RedHat Linux 7.1, kernel 2.4.31-i386, windows, others.
JDK Version: 1.3.1_03, others

There is a problem with jboss-3.0.0RC1_tomcat-4.0.3
where including the home and remote (or local-home and
local) EJB interfaces in the WAR file causes a NPE
during
StatelessSessionContainer$ContainerInterceptor.invokeHome.

Removing the EJB interfaces from the WAR file causes
the problem to dissappear.

Not sure if this is a JBoss "unified classloader"
problem or a catalina servlet 2.3 classloader problem,
or a mix.

This problem does not happen with JBoss2.4 + catalina.

*Lots* of people have complained about this on the
email lists under different subject titles, but here is
a link to one as an example, which also includes a
stack trace:

http://www.mail-archive.com/jboss-user@lists.sourceforge.net/msg15351.html

This bug is a killer for people who need to keep their
application bundles cross-appserver compatible.

Thanks!
David

----------------------------------------------------------------------

>Comment By: Scott M Stark (starksm)
Date: 2002-04-25 11:59

Message:
Logged In: YES 
user_id=175228

Only the NPE is a bug. When fixed this will result in a 
ClassCastException due to the default optimization of 
servlet to ejb call and the fact that duplicate classes are 
included in the ear, and the servlet 2.3 class loading 
model which will load the war level classes before those 
visible to the web context parent class loader. In 3.0 the 
behavior of downgrading a call to use serialization when 
incompatibles classes where seen was dropped. It would be a 
request for enhancement to or a seperate bug to restore 
this behavior.

It is not a violation of any j2ee spec to not include the 
ejb interfaces in the war. The 1.3 j2eeri will deploy such 
an ear that includes a jsp page calling an ejb. The 1.3 
j2eeri will also deploy a war that does include the ejb 
interfaces in the war. Compatability with such a packaging 
should be supported.

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=548668&group_id=22866

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to