Bugs item #642250, was opened at 2002-11-22 12:04
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=642250&group_id=22866

Category: JBossMX
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Phil Cornelius (smapjb)
Assigned to: Scott M Stark (starksm)
Summary: CNFE Jdom

Initial Comment:
I have submitted this ear following the thread on
jboss-user included below.

The submitted ear works on Jboss-3.0.2 but not on 3.0.4

<SNIP>
3.0.4 should work, and does for the jbosstest-web.ear
which I updated to
include a servlet that accesses a class loaded from a
jar referenced by an
ejb-jar manifest Class-Path entry. If you have an ear
that demonstrates the
problem that you can submit to sourceforge open a bug
and include the ear.


xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx

----- Original Message ----- 
From: "Phil Cornelius" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 18, 2002 2:35 AM
Subject: Re: [JBoss-user] JBoss 3.0.4 w/ Jetty Classloader

Attached.

I have however solved this by adding a copy of the
manifest that is in
the ejb jar to the war file (details in thread).

So the question I have now is should the servlets have
been able to find
the jdom classes in 3.0.2?

Yours
Phil





On Fri, 2002-11-15 at 17:19, Scott M Stark wrote:
> Show the complete stack trace of the CNFE coming from
the servlet. The
> indentation of the ear is not coming through in this
mail well so run the
> attached class on it and send that.
> 
> xxxxxxxxxxxxxxxxxxxxxxxx
> Scott Stark
> Chief Technology Officer
> JBoss Group, LLC
> xxxxxxxxxxxxxxxxxxxxxxxx
> 
> ----- Original Message ----- 
> From: "Phil Cornelius" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, November 15, 2002 1:43 AM
> Subject: RE: [JBoss-user] JBoss 3.0.4 w/ Jetty
Classloader
> 
> 
> > Actually now you mention it.. I noticed something too..
> > 
> > My app is structured thus:
> > 
> > -myear.ear
> > -lib/
> > jdom.jar
> > junit.jar
> > +blah.war
> > -blah.jar
> > -META-INF/
> > Manifest.mf
> > +otherstuff
> > +META-INF/
> > 
> > 
> > In the manifest of my ejb jar I have
> > 
> > Manifest-Version:1.0
> > Class-Path: ./lib/jdom.jar ./lib/junit.jar
> > 
> > Now in Jboss-3.0.2 everything works fine and my
servlets can access the
> > jdom classes..
> > 
> > However in Jboss-3.0.4 I get ClassNotFound
org.jdom.Element thrown from
> > my servlets.
> > 
> > I had a sniff around.. currently I am happy that it
works with 3.0.2..
> > 
> > Can anyone shed light on this?
> > Is there anything that I need to set in my WAR file
like a Manifest.mf?
> > 
> > I want to keep my third party libs in one place and
I don't want to
> > clutter the Jboss dist. so I want to avoid putting
a copy in WEB-INF/lib
> > 
> > Yours
> > Phil
</SNIP>

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

>Comment By: Phil Cornelius (smapjb)
Date: 2002-11-25 09:07

Message:
Logged In: YES 
user_id=559447

JDK 1.4.1_01 on W2K.

The exeption is thrown when the servlet is invoked..

http://localhost:8080/jdomtest/TestJDom

I didn't include an EJB jar with manifest because I was able
to reproduce the problem without. 

I am still unclear: why should it work? i.e. I am happy that
I am required to add a classpath directive to the manifest
of the war file.. so in a sense I am happy that it does not
work in 3.0.4.

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

Comment By: Scott M Stark (starksm)
Date: 2002-11-24 02:44

Message:
Logged In: YES 
user_id=175228

I have tried deploying the attached ear using both JDK 
1.3.1_05 and JDK 1.4.1_01 with jboss-3.0.4 on a WinXP 
system and both work fine. The deployment info is shown 
below. What is the JVM and OS on which you see a 
problem?

19:37:24,379 INFO  [Server] JBoss (MX MicroKernel) [3.0.4 
Date:200211021607] Started in 0m:18s:807ms
19:37:49,405 INFO  [MainDeployer] Starting deployment of 
package: file:/C:/tmp/JBoss/jboss-
3.0.4/server/default/deploy/testear.ear
19:37:49,415 INFO  [EARDeployer] Init J2EE application: 
file:/C:/tmp/JBoss/jboss
-3.0.4/server/default/deploy/testear.ear
19:37:49,505 INFO  [jbossweb] Registered 
jboss.web:Jetty=0,JBossWebApplicationContext=5,context=/j
domtest
19:37:49,525 INFO  [jbossweb] Extract 
jar:file:/C:/tmp/JBoss/jboss-3.0.4/server/
default/tmp/deploy/server/default/deploy/testear.ear/59.testear
.ear-contents/web
stuff.war!/ to 
C:\WINDOWS\TEMP\Jetty_0_0_0_0_8080__jdomtest\webapp
19:37:49,945 INFO  [jbossweb] Started 
WebApplicationContext[/jdomtest,testWeb]
19:37:49,965 INFO  [jbossweb] successfully deployed 
file:/C:/tmp/JBoss/jboss-3.0
.4/server/default/tmp/deploy/server/default/deploy/testear.ear/5
9.testear.ear-contents/webstuff.war to /jdomtest
19:37:49,965 INFO  [MainDeployer] Deployed package: 
file:/C:/tmp/JBoss/jboss-
3.0.4/server/default/deploy/testear.ear

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

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


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to