Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <22135480.1171994045816.JavaMail.jira@brutus>
Date: Tue, 20 Feb 2007 09:54:05 -0800 (PST)
From: "Aman Nanner (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GERONIMO-2742) Deployer cannot access libaries
 in shared/lib and shared/classes
In-Reply-To: <10745727.1168984887882.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/GERONIMO-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474510 ] 

Aman Nanner commented on GERONIMO-2742:
---------------------------------------

This is a custom GBean class of mine that references the geronimo code.   As a workaround to the sharedlib issue, I had put my custom GBean classes in a "dummy" EJB module in my application EAR folder.  With this setup, there were no classloading issues, although my preference was to put my GBean classes in the /shared/classes app so that I didn't have to use a dummy EJB module.

In our development environment, our EAR app is fully exploded and each WAR folder and EJB JAR folder is actually a symlink to its respective module directory in our Eclipse environment.  So we don't use any actual JAR archives in the dev version of our app (except for third-party libraries).  This is why I am avoiding putting the GBean custom code in the repository for now, because as far as I know, the repository requires the classes to be in JARs.

I don't think you'd need to put the connector module as a parent of the shared lib module just for this issue.  I will probably stick with the "dummy" EJB module method for now and scrap using the /shared/lib and /shared/classes folders altogether.

> Deployer cannot access libaries in shared/lib and shared/classes
> ----------------------------------------------------------------
>
>                 Key: GERONIMO-2742
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2742
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 1.2
>         Environment: Windows XP, Geronimo 1.2-beta
>            Reporter: Aman Nanner
>         Attachments: sharedlib-2.0.zip, sharedlib.zip, testing.ear.zip
>
>
> It seems that when running the deployer to deploy my EAR file, the classloaders during deployment cannot access the shared/lib and shared/classes directory.  My app has dependencies on libraries that are stored in both shared/classes and shared/lib.  Because these libraries cannot be found, the deployment fails.
> Neither regular deployment nor hot deployment works.  My EAR file used to hot deploy properly in Geronimo 1.1.1 (I never used the regular deployer in 1.1.1, so I don't know if that would have worked too).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.