Re: Deployment pblm in G1.1

2006-04-13 Thread Dave Colasurdo
I'm seeing a different result with a simple HelloWorld.war test. It deploys fine on G1.0 but doesn't on G1.1.. I've tried on both linux and windows... I've attached the war.. # java -jar deployer.jar --user system --password manager deploy /home/davecola/HelloWorld/HelloWorld.war

Re: commons logging issue

2006-04-13 Thread Guilherme Rios
Thanks Pablo, Should this be addressed? The practical impact is sometimes an application will deploy fine in Geronimo/Tomcat but not Geronimo/Jetty (because it will use jars unavailable in the former) or the other way around (because app jars will conflict with Geronimo's, as already

Re: commons logging issue

2006-04-13 Thread Dain Sundstrom
Our long term goal is to isolate web applications from the system classes. This means that by default a web application will only see the spec jars required by the servlet spec. Then if an application needs more jars, they can either add them to the WEB-INF/lib or the geronimo repository

RE: commons logging issue

2006-04-13 Thread Clough, Ray C PWR
I have found that if the commons-logging.jar file is in my app's lib directory, then Geronimo chokes on it. However, deployments of the exact same WAR file on Tomcat, Sun, Oracle servers work fine if the commons-logging.jar file is present. I always figured it was a class loader error in

RE: JMS Connector deployment for SPECjAppServer2004

2006-04-13 Thread Zakharov, Vasily M
The name-gbean-link issue is no more important for SjAS, but it looks like a bug to me anyway, so I filed it to Jira as http://issues.us.apache.org/jira/browse/GERONIMO-1841 Vasily -Original Message- From: Zakharov, Vasily M [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 04, 2006

Re: Deployment pblm in G1.1

2006-04-13 Thread Dave Colasurdo
Dain, I just rebuilt the server and the application (from scratch)and am now seeing the same behavior you describe on Jetty. Simple applications deploy either with or without a plan... Though an exception is thrown for both cases.. This behavior is consistent when a plan is specified for

Re: commons logging issue

2006-04-13 Thread Guilherme Rios
Ray, If I understood the discussions around this topic that happened this week, the problem you noticed has to do with conflicts between WEB-INF/lib jars and Geronimo jars, because currently they share the same classloader. Sticking to the track of this thread, you may try to deploy your

RE: commons logging issue

2006-04-13 Thread Clough, Ray C PWR
Thanks. I thought it seemed like a classloader bug! Nice to know I was right. I've taken to using Ant magic to remove it from the Geronimo-build WAR file. - Ray Clough -Original Message- From: Guilherme Rios [mailto:[EMAIL PROTECTED] Sent: Thursday, April 13, 2006 3:39 PM To: