I really don't know why it is not working for you. There might be some configuration difference that we both consider irrelevant for this, and for that reason miss to recognize. Anyway, I wrote a small test application to verify that my setup still works in 3.0.6. It works on my installation (Jboss 3.0.6 unzipped and no configuration touched, jdk 1.4.1, windows 2000).

I have attached the ear file and a zip file with the java sources. Please don't judge my general coding from theses sources since they were only built to test just this dependency configuration issue. I would be very interested to see if it works ok on your configuration, and if not, to learn what the difference might be.

The application includes:
- a third party library jar (jakarta-regexp)
- a library jar of my own with just one class.
- an ejb jar with a stateless session bean using classes from both library jars.
- a web application war using library classes from both library jars in calls to the stateless session bean. (using only local ref for regexp since it the RE class is not serializable, but using both local and remote ref when using the test class in my own library)

Just deploy the ear and hit the root context. This should give you an ugly html form with three input fields. Enter any string in the first one and give a regexp pattern an a text to split using the pattern in the second and third ones. submit and it should return some text.

I haven't tested class path dependencies on weblogic, but I'll probably have the opportunity next week to test on both Websphere and Sybase EAServer.

I'm really not trying to prove you wrong, I'm just informing about how I made it work for our required dependencies hoping it might help someone with similar requirements.

Sincerely
/Fredrik Lindgren


Rod Macpherson wrote:
Fredrik, here's a little background. We know the jars in application.xml are
for application clients and that we should not put utility jars there -
whether it is the perfect location for such information or not. I have made
that point made and Craig just reiterated it. The prescribed solution is to
use Class-Path because that construct already existed for downloadable
jars - in my opinion that was not a good decision. That ground has been
covered ad nauseam. Therein lies the problem: it fails on weblogic it fails
on 3.0.2 of JBoss and Craig has just reported that it fails on 3.0.4 and
3.0.6. Since I have never seen a working example of Class-Path loads being
effective I tend to discount your claim that is works. I am sure the
application works but I am suspicious that it works because you have
specified the utility jars that way. I would hasten to add it fails and has
always failed in WebLogic 6.X service pack X. I will personally recommend
you for guru-dom if you can tell me what Craig and I are doing wrong in
setting this up but you have to admit tying shoe laces is more difficult
that adding a jar path to Class-Path :)

----- Original Message -----
From: "Fredrik Lindgren" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, February 01, 2003 3:57 AM
Subject: Re: [JBoss-user] EAR works in 2.4.10 but not in 3.0.6



You should not put these jars in application.xml, that's for application
clients. You should however put the class path entries in the manifest
files of the WARs and ejb jars that depend on the common library jars. I
have not tested on 3.0.6, but I definately have it working in 3.0.4

/Fredrik Lindgren (not a JBoss guru, but hopefully helpful anyway)

Rod Macpherson wrote:

I vote they formalize the <java> module as a clean, intuitive and

elegant

mechanism for placing utility jars in EAR scope.

----- Original Message -----
From: "Demyanovich, Craig - Apogent" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 31, 2003 6:47 PM
Subject: RE: [JBoss-user] EAR works in 2.4.10 but not in 3.0.6




3.0.4 did not work either.  Like Rod, the EAR will work if I include all
library JARs in application.xml as <java> modules.  According to the FAQ
that I cited earlier
(http://www.jboss.org/faq.jsp#FAQ-BEANDEV-NORMALJARS),


though, the use of application.xml is NOT appropriate.  However, I know

of

no other way to create a single deployment unit for my application.  I
appeal to you again, JBoss gurus, please explain!!!

Thanks for your time,
Craig


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user




-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user



Attachment: test.ear
Description: Binary data

Attachment: src.zip
Description: Zip compressed data

Reply via email to