Re: deployer offline mode on 1.2 branch?

2006-11-27 Thread Sachin Patel
I was supposed to do this, but since this was a hack, was going to  
take a look one more time to see why this was occurring but never got  
around to it.  If you want, take a look at my earlier thread on the  
offline deployer to see where my debugging last got me.  Another pair  
of eyes would help.


I remember the previous gbean started ok in the same configuration  
which also required xmlbeans, but the second gbean failed with the  
exception which I couldn't figure out the underlying cause.


On Nov 22, 2006, at 12:23 PM, David Jencks wrote:



On Nov 22, 2006, at 9:07 AM, toby cabot wrote:


Hi Folks,

I'd like to use the 1.2 deployer's offline mode (and hopefully the
distribute command) but it's not working out-of-the-box at the  
moment.

Is it supposed to, or is it a non-feature?  I could get it to work by
running it like so:

$ java -Djava.ext.dirs=/tmp/g/repository/stax/stax-api/1.0:/tmp/g/ 
repository/xmlbeans/xbean/2.0.0 -jar /tmp/g/bin/deployer.jar -- 
offline list-modules


... otherwise it can't find org/apache/xmlbeans/XmlObject and
javax/xml/stream/XMLStreamException.  If this is supposed to work  
then

I'd imagine that we'd want to add these jars to the deployer's jar
manifest classpath.  I can take a look at doing this if someone could
point me to the part of the build process that jars deployer.jar.


I'm not surprised that it doesn't work but I am very surprised your  
fix worked :-)


I thought the problem would be that the files var/config/offline- 
deployer-list didn't have all the new deployer configs we came up  
with in them.


Can you investigate whether the xmlbeans stuff got into the  
classpath through manifest classpath entries in 1.1 which I think  
is the last time offline deployment was tested?


thanks
david jencks



Thanks,
Toby





-sachin




Re: deployer offline mode on 1.2 branch?

2006-11-22 Thread toby cabot
Hi David,

On Wed, Nov 22, 2006 at 09:23:24AM -0800, David Jencks wrote:
> I'm not surprised that it doesn't work but I am very surprised your  
> fix worked :-)

Sometimes blind squirrels find nuts ;)

> Can you investigate whether the xmlbeans stuff got into the classpath  
> through manifest classpath entries in 1.1 which I think is the last  
> time offline deployment was tested?

It looks as if comes from somewhere else:

1.1.1 deployer.jar manifest Class-Path:
../lib/geronimo-common-1.1.1.jar
../lib/geronimo-deployment-1.1.1.jar
../lib/geronimo-deploy-jsr88-1.1.1.jar
../lib/geronimo-deploy-tool-1.1.1.jar
../lib/geronimo-kernel-1.1.1.jar
../lib/geronimo-system-1.1.1.jar
../lib/geronimo-util-1.1.1.jar
../lib/geronimo-j2ee-deployment_1.0.1_spec.jar
../lib/cglib-nodep-2.1_3.jar
../lib/commons-cli-1.0.jar
../lib/commons-logging-1.0.4.jar
../lib/log4j-1.2.8.jar../lib/mx4j-3.0.1.jar
../lib/mx4j-remote-3.0.1.jar
../lib/xpp3-1.1.3.3.jar
../lib/xstream-1.1.3.jar 
server.jar

1.2 deployer.jar manifest Class-Path:
../lib/geronimo-common-1.2-SNAPSHOT.jar
../lib/geronimo-kernel-1.2-SNAPSHOT.jar
../lib/geronimo-system-1.2-SNAPSHOT.jar
../lib/geronimo-util-1.2-SNAPSHOT.jar
../lib/geronimo-deployment-1.2-SNAPSHOT.jar
../lib/geronimo-deploy-jsr88-1.2-SNAPSHOT.jar
../lib/geronimo-deploy-tool-1.2-SNAPSHOT.jar
../lib/geronimo-j2ee-deployment_1.1_spec-1.0.1.jar
../lib/mx4j-3.0.1.jar
../lib/mx4j-remote-3.0.1.jar
../lib/commons-cli-1.0.jar
../lib/commons-logging-1.0.4.jar
../lib/cglib-nodep-2.1_3.jar
../lib/log4j-1.2.13.jar
../lib/jline-0.9.9.jar
../lib/xpp3-1.1.3.3.jar
../lib/xstream-1.1.3.jar
../lib/endorsed/xercesImpl-2.6.2.jar
../lib/endorsed/xmlParserAPIs-2.6.2.jar
server.jar

Strangely, I can get the two jars I need into the manifest (and lib/
directory) by adding them as classpath elements in online-deployer's
pom.xml.  I doubt that's kosher, but it seems to work.

Thanks,
Toby


Re: deployer offline mode on 1.2 branch?

2006-11-22 Thread David Jencks


On Nov 22, 2006, at 9:07 AM, toby cabot wrote:


Hi Folks,

I'd like to use the 1.2 deployer's offline mode (and hopefully the
distribute command) but it's not working out-of-the-box at the moment.
Is it supposed to, or is it a non-feature?  I could get it to work by
running it like so:

$ java -Djava.ext.dirs=/tmp/g/repository/stax/stax-api/1.0:/tmp/g/ 
repository/xmlbeans/xbean/2.0.0 -jar /tmp/g/bin/deployer.jar -- 
offline list-modules


... otherwise it can't find org/apache/xmlbeans/XmlObject and
javax/xml/stream/XMLStreamException.  If this is supposed to work then
I'd imagine that we'd want to add these jars to the deployer's jar
manifest classpath.  I can take a look at doing this if someone could
point me to the part of the build process that jars deployer.jar.


I'm not surprised that it doesn't work but I am very surprised your  
fix worked :-)


I thought the problem would be that the files var/config/offline- 
deployer-list didn't have all the new deployer configs we came up  
with in them.


Can you investigate whether the xmlbeans stuff got into the classpath  
through manifest classpath entries in 1.1 which I think is the last  
time offline deployment was tested?


thanks
david jencks



Thanks,
Toby




deployer offline mode on 1.2 branch?

2006-11-22 Thread toby cabot
Hi Folks,

I'd like to use the 1.2 deployer's offline mode (and hopefully the
distribute command) but it's not working out-of-the-box at the moment.
Is it supposed to, or is it a non-feature?  I could get it to work by
running it like so:

$ java 
-Djava.ext.dirs=/tmp/g/repository/stax/stax-api/1.0:/tmp/g/repository/xmlbeans/xbean/2.0.0
 -jar /tmp/g/bin/deployer.jar --offline list-modules

... otherwise it can't find org/apache/xmlbeans/XmlObject and
javax/xml/stream/XMLStreamException.  If this is supposed to work then
I'd imagine that we'd want to add these jars to the deployer's jar
manifest classpath.  I can take a look at doing this if someone could
point me to the part of the build process that jars deployer.jar.

Thanks,
Toby