[jira] Commented: (GERONIMO-2742) Deployer cannot access libaries in shared/lib and shared/classes

2007-02-07 Thread Rakesh Midha (JIRA)

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

Rakesh Midha commented on GERONIMO-2742:



I tried using sharedlib and it works fine for me.

Are you sure you added in your plan file



sharedlib




If that's not a problem than please provide more details on setup, and if 
possible share your ear file and libraries

> 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
>
> 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.



[jira] Commented: (GERONIMO-2742) Deployer cannot access libaries in shared/lib and shared/classes

2007-02-08 Thread Rakesh Midha (JIRA)

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

Rakesh Midha commented on GERONIMO-2742:



Hello Aman

Thanks for the files.

I think there is no problem with sharedlib. The problem is in your jar files 
class org.jgroups.MembershipLister is missing.

Here is how I can prove it: (case 1)
1. unzip your sharedlib.zip file in sharedlib directory
2. try to deploy testing.ear
It gives noclassdeffound for org/jgroups/MembershipListner

Now...(case 2)
1. delete unziped jar files from sharedlib directory
2. try to deploy testing.ear
It gives noclassdeffound for org/jboss/cache/TreeCacheMBean

which means in case 1. org/jboss/cache/TreeCacheMBean is found by 
org/jgroups/MembershipListner us not
try adding that file.

Please try and let me know if it works? I think it should.

Thanks
Rakesh


> 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.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.



[jira] Commented: (GERONIMO-2742) Deployer cannot access libaries in shared/lib and shared/classes

2007-02-08 Thread Aman Nanner (JIRA)

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

Aman Nanner commented on GERONIMO-2742:
---

Hi Rakesh,

I neglected to include the jgroups.jar archive, which is why you were getting 
the NoClassDefFound error for org.jgroups.MembershipListener.

I'm surprised that you got that far thoughmy deployment was still failing 
with a NoClassDefFound error on org.jboss.cache.TreeCacheMBean.  I am currently 
testing this against Geronimo 1.2-beta, and using "offline" and "inPlace" 
deployment.

It seems that, during runtime, the server can pick up the classes from the 
shared lib folder, but the deployment process cannot for some reason.

> 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.



[jira] Commented: (GERONIMO-2742) Deployer cannot access libaries in shared/lib and shared/classes

2007-02-08 Thread David Jencks (JIRA)

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

David Jencks commented on GERONIMO-2742:


I would guess that this problem is caused by the shared lib configuration not 
being started when the deployer is working.  Therefore I'd expect offline 
deployment to not work without an update to what gets started for the offline 
deployer, but I'm a bit surprised online deployment isn't working.  Can you 
check if the shared lib config is started and if not see if that fixes the 
problem?

> 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.



[jira] Commented: (GERONIMO-2742) Deployer cannot access libaries in shared/lib and shared/classes

2007-02-08 Thread Rakesh Midha (JIRA)

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

Rakesh Midha commented on GERONIMO-2742:



Hello 

With your new sharedlib your application is getting deployed without any 
problem. I  tried normal deployment. 

As David suggested, check if 
org.apache.geronimo.configs/sharedlib/2.0-SNAPSHOT/car is started on your 
server. try it and let us know if problem persists.

Thanks
Rakesh

> 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.



[jira] Commented: (GERONIMO-2742) Deployer cannot access libaries in shared/lib and shared/classes

2007-02-09 Thread Aman Nanner (JIRA)

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

Aman Nanner commented on GERONIMO-2742:
---

Ok, server deployment worked for me too...I'm not sure why it didn't work for 
me earlier.

The "offline" deployment still produces the same problem for me, and this is 
the deployment method we use in our build scripts.  Can you try to reproduce 
the problem using "offline" deployment?

Thanks,
Aman

> 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.



[jira] Commented: (GERONIMO-2742) Deployer cannot access libaries in shared/lib and shared/classes

2007-02-15 Thread Rakesh Midha (JIRA)

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

Rakesh Midha commented on GERONIMO-2742:



Try adding org.apache.geronimo.configs/sharedlib/2.0-SNAPSHOT/car  in 
/var/config/offline-deployer-list if you want to use sharedlib with offline 
build.

If you face an error specified in 
http://issues.apache.org/jira/browse/GERONIMO-2765 please let us know, 
otherwise things should work fine for you.

Thanks
Rakesh



> 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.



[jira] Commented: (GERONIMO-2742) Deployer cannot access libaries in shared/lib and shared/classes

2007-02-20 Thread Aman Nanner (JIRA)

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

Aman Nanner commented on GERONIMO-2742:
---

Hi,

I added the sharedlib configuration to the offline-deployer-list and it solved 
this particular issue.  Thanks for the info.

My deployment is failing on another issue now.  I have a class in 
/shared/classes that imports "org.apache.geronimo.connector.AdminObjectSource". 
 However, during deployment I get a NoClassDefFoundError because the deployer 
cannot find the "org.apache.geronimo.connector.AdminObjectSource" class.  I'm 
guessing that the deployer does not have access to the repository when 
processing a class in /shared/classes.  This happens with BOTH offline and 
server deployment.

> 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.



[jira] Commented: (GERONIMO-2742) Deployer cannot access libaries in shared/lib and shared/classes

2007-02-20 Thread David Jencks (JIRA)

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

David Jencks commented on GERONIMO-2742:


If you are using and extending core geronimo classes you are really extending 
geronimo rather than just deploying a ee app.  We could fix this by including 
the connector module as a parent of the shared lib module but I think it would 
be more appropriate for you to add your jars to the geronimo repository and 
construct a module that includes your jars and whatever parts of the geronimo 
server it needs as dependencies, and to use this instead of the shared lib.  If 
you do this you won't have to deal with changing the offline deployer list 
either.

> 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.



[jira] Commented: (GERONIMO-2742) Deployer cannot access libaries in shared/lib and shared/classes

2007-02-20 Thread Aman Nanner (JIRA)

[ 
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.



[jira] Commented: (GERONIMO-2742) Deployer cannot access libaries in shared/lib and shared/classes

2007-02-20 Thread David Jencks (JIRA)

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

David Jencks commented on GERONIMO-2742:


So it sounds to me as if the ideal solution here would be an "eclipse-aware" 
repository where some repo entries actually pointed to eclipse workspaces 
rather than jars in the maven-layout file based repo?  We do something sort of 
similar for the in-place deployment of j2ee artifacts and sachin did some work 
on integrating eclipse with j2ee deployment..

> 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.



[jira] Commented: (GERONIMO-2742) Deployer cannot access libaries in shared/lib and shared/classes

2007-02-20 Thread Aman Nanner (JIRA)

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

Aman Nanner commented on GERONIMO-2742:
---

An Eclipse-aware repository is a possibility, although the solution for this 
issue doesn't have to be that heavy.  If the maven-style layout could be 
modified such that a folder with a maven-style name, rather than a JAR, could 
be used, then that would solve the problem as I could create a symlink for that 
folder.

Example:

In the repository,  consider 
org/apache/geronimo/modules/geronimo-connector/1.2-beta/geronimo-connector-1.2-beta.jar.
  The "geronimo-connector-1.2-beta.jar" could be a folder name instead of a JAR 
archive, and the classes would be in exploded format within this folder.  Then 
"geronimo-connector-1.2-beta.jar" could be made into a symlink that points to a 
folder within the Eclipse workspace.

I'm not sure how doable this is, since I don't know if you use a third-party 
library (Maven?) for repository classloading.  But this is along the lines of 
what I was thinking.

> 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.



[jira] Commented: (GERONIMO-2742) Deployer cannot access libaries in shared/lib and shared/classes

2007-02-21 Thread Rakesh Midha (JIRA)

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

Rakesh Midha commented on GERONIMO-2742:



Hello Aman

>From what I know and from the simple test I did on repository. I don't think 
>there is any problem in having directory named geronimo-connector-1.2-beta.jar 
>(the name same as jar file), I think you need to add META-INF and manifest.mf 
>files in directory . This directory will be treadted in same way as if it is a 
>jar file.

This directory could be a symb link as you said, thought never tried this but i 
don't see any problem in it.

Have you tried doing this, I think you should not face any problem with this.

thanks
Rakesh


> 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.



[jira] Commented: (GERONIMO-2742) Deployer cannot access libaries in shared/lib and shared/classes

2007-02-22 Thread Aman Nanner (JIRA)

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

Aman Nanner commented on GERONIMO-2742:
---

That's good to know that having an exploded directory should work.  I have not 
yet tried it yet, but it seems like it is outside the scope of this JIRA issue 
now, so the issue can be closed.

> 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.