We actually found the same problem in our company's application. Is
this something that should be changed in Jasper?
danch wrote:
> I believe that the ClassNotFound exceptions are limited to when Jasper
> (the Tomcat JSP engine) calls out to javac to compile the JSP - when
> the code actually runs in JBoss/Tomcat, the interface classes are
> loaded from the EJB-jar's classloader. Not that this helps you make a
> portable ear...
>
> -danch
>
> Matthew Devaney wrote:
>
>> The documentation for weblogic, as shown at:
>> http://e-docs.bea.com/wls/docs60/ejb/EJB_deployover.html
>> .. talks about the class loader issues I mentioned, in particular the
>> section on Diagnosing ClassCastException errors it states:
>> "To correct such ClassCastException errors, EJB and servlet developers
>> must ensure that no two classloaders ever load an identical class.
>> Specifically, you should always ensure that EJB classes reside only
>> in the
>> deployed EJB .jar file or EJB directory, and that they are not
>> included in
>> other EJB .jar files or classpath definitions."
>>
>> If we assume that EJB classes includes the interfaces, and take into
>> account
>> the fact it talks about servlets and this particular error in the lines
>> immediatly above.. my reading of it is that it's saying don't include
>> EJB
>> classes in the web app either.. (Although if someone thinks I'm
>> misinterpreting, I'm more than happy to believe that given a reasonable
>> reason :)
>>
>> Any thoughts?
>> .Matt
>>
>>> -----Original Message-----
>>> From: Allen fogleson [mailto:[EMAIL PROTECTED]]
>>> Sent: 18 June 2001 14:51
>>> To: [EMAIL PROTECTED]
>>> Subject: Re: [JBoss-user] quick tutorial
>>>
>>>
>>> Hmmm well I think you could include them in the lib directory, it isnt
>>> platform independent then, but it should work in JBoss. (I havent
>>> tested
>>> that)
>>>
>>> Those classes do have to be available to the client, be it an
>>> application
>>> client or a web client, so they should be in the war file. I
>>> deployed the
>>> example on weblogic 6 and didnt get any errors, I havent tested any
>>> other
>>> containers though.
>>>
>>> Al
>>>
>>> ----- Original Message -----
>>> From: Matthew Devaney <[EMAIL PROTECTED]>
>>> To: <[EMAIL PROTECTED]>
>>> Sent: Monday, June 18, 2001 7:25 AM
>>> Subject: RE: [JBoss-user] quick tutorial
>>>
>>>
>>>
>>>> Hi,
>>>> Thanks for the example Al, but is there anyway to get it working
>>>
>>>
>>> without
>>>
>>>> including the ejb home and remote classes inside the WAR file?.
>>>>
>>>> The reason for wanting to do this is that I've been given
>>>
>>>
>>> to understand
>>> that
>>>
>>>> doing so can cause class loader exceptions when using the
>>>
>>>
>>> ear file in
>>> other
>>>
>>>> containers. This is due to the container trying to load the
>>>
>>>
>>> same class
>>> twice
>>>
>>>> (once from the EJB, once from the war file)
>>>>
>>>> So far my attempts at something like this at JBoss 2.2.2
>>>
>>>
>>> have all met with
>>>
>>>> classNotFound exceptions within the jsp page during compile
>>>
>>>
>>> time - however
>>>
>>>> it seemed to work without problems at JBoss 2.2.1.
>>>>
>>>> Thanks,
>>>> Matt
>>>>
>>>>
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
