geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jcaristi <jcari...@whisolutions.com>
Subject Re: [DISCUSS] URLClassloader problem
Date Tue, 30 Sep 2008 13:15:48 GMT

Removing the <moduleId> worked!  We may also try the other technique, but for
now we're OK.


Kevan Miller wrote:
> 
> 
> Understood.
> 
> Tim had mentioned to me that he was working on an Axis2 patch. I'm  
> sure he'll let us know where he stands with this work.
> 
> You could try removing the <moduleId> of your geronimo deployment  
> plan. That should allow redeployment to at least work... The undeploy  
> part will be slow (as it tries to delete the jar files), but deploy  
> should create a new unique default/<archive-name>/<random-number/war  
> module. So, should at least "work". Certainly, still a "headache",  
> will let you decide how it compares to your current *headache*. You'll  
> eventually run out of PERMGEN space... Your repository directory will  
> fill up with default/<archive-name> directories, also
> 
> There's always the option of deploying your Axis2 libraries separately  
> and declaring a dependency in your web app deployment plan... This  
> should work perfectly (except your changing the contents of your WAR  
> file, and not just defining a geronimo deployment plan). Hmm.  
> Actually, could you leave your WAR contents unchanged and still use  
> this technique?
> 
> --kevan
> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/-DISCUSS--URLClassloader-problem-tp19448428s134p19741889.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.


Mime
View raw message