geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Mulder <ammul...@alumni.princeton.edu>
Subject Re: Geronimo :: Derby :: Connector compile error
Date Tue, 16 Nov 2004 21:50:07 GMT
	The deployer hierarchy was changed but unfortunately now no 
deployer is started by default.  I think if you add 
org/apache/geronimo/RuntimeDeployer to the server command line then the 
deployer should work again.

Aaron

On Tue, 16 Nov 2004, Craig Johannsen wrote:

> Thanks, David.
> 
> maven m:update m:build worked with just a few hiccups.  Had to go into 
> derby-connector and run "maven" to build the rar.
> 
> Some security tests that were failing yesterday succeeded today.
> 
> My Hello session bean doesn't deploy to the running server using the 
> following command:
>     java -jar $GERONIMO_HOME/bin/deployer.jar --user system --password 
> manager deploy hello.jar
> The deployer reports:
> Deployment failed
>   Server reports: No deployer present in kernel
> 
> Manually specifying org/apache/geronimo/DeployerSystem in the server 
> startup command doesn't seem to help.
> 
> The hello.jar had previously been deployed successfully using the command:
>     java -jar $GERONIMO_HOME/bin/deployer.jar distribute hello.jar
> It subsequently runs OK.
> 
> Cheers,
> Craig
> 
> David Jencks wrote:
> 
> > We had some classloader problems with the original handling of the  
> > exception sorters, and it looks like perhaps only a partial fix got  
> > applied.
> >
> > I've just updated both the geronimo derby-connector and  
> > tranql-connector with a version I like.  If you rebuild both it 
> > should  work.
> >
> > I can't remember what our process on this is supposed to be.  Should 
> > I  update the openejb maven repo by hand with the updated tranql 
> > connector  jar or is this done automatically?
> >
> > thanks
> > david jencks
> >
> 
> 

Mime
View raw message