RE: [JBoss-user] "could not be found": jar in .ear file

[Danny . Yates]

Title: Message

I don't think you need the "./" in the path. Just the JAR names.

 

 

--

Danny Yates

 

-----Original Message-----
From: Bill Milbratz [mailto:[EMAIL PROTECTED]
Sent: 22 September 2003 18:00
To: '[EMAIL PROTECTED]'
Subject: [JBoss-user] "could not be found": jar in .ear file

Hi,

How do you tell Jboss3 to refer to a jar within an ear file? This works fine on Jboss2 and Weblogic 6 and 7. I've searched the documentation and archives, but don't see an obvious way to get past this problem, aside from copying the jars into the 'deploy' directory.

(The section "Deployers and Classloaders" in the 3.2.1 documentation seems to point to an answer...but doesn't discuss how the jars are loaded from the file system JBOSS_DIST/server/<config>/deploy directory .)

We're upgrading from jboss 2.4.6 to Jboss 3.2.1. Our ear file contains several jars and a manifest that points to those .jars. The log has several "could not be opened"

Manifest entry (this has the required newline at the end):
Class-Path: ./activation.jar ./commons-beanutils.jar

Server log:
2003-09-22 10:11:21,327 DEBUG [org.jboss.deployment.MainDeployer] new manifest entry for sdi at pe.ear entry is activation.jar

2003-09-22 10:11:21,327 WARN  [org.jboss.deployment.MainDeployer] The manifest entry in file:/C:/projects/devtools/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/pe.ear references URL file:/C:/projects/devtools/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/activation.jar which could not be opened, entry ignored

thanks,

bill milbratz

_____________________________________________________________________

Notice to recipient:

The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.

When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity.

If this email originates from the U.K. please note that Bank of America, N.A., London Branch, Banc of America Securities Limited and Banc of America Futures Incorporated are regulated by the Financial Services Authority.

_____________________________________________________________________