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 22:33:07 GMT
	Actually, it looks like I checked in a change to add the deployer
a little while ago.  So perhaps you hadn't done a full rebuild since then
or something.  In any case, the very latest builds should start the
runtime deployer by default.

Aaron

On Tue, 16 Nov 2004, Craig Johannsen wrote:

> Thanks, Aaron. That worked.
> 
> The server was started with:
> java -jar $GERONIMO_HOME/bin/server.jar org/apache/geronimo/DebugConsole 
> org/apache/geronimo/RuntimeDeployer
> 
> The Hello session bean was deployed with:
> java -jar $GERONIMO_HOME/bin/deployer.jar --user system --password 
> manager deploy hello.jar
> 
> Which resulted in the server reporting:
> 14:09:11,322 INFO [LocalConfigStore:config-store] Installed 
> configuration hello in location 74
> 14:09:11,400 INFO [ConfigurationManagerImpl] Loaded Configuration 
> geronimo.config:name="hello"
> 14:09:11,967 INFO [Configuration] Started configuration hello
> 14:09:12,172 INFO [GenericEJBContainer] GenericEJBContainer 
> 'geronimo.server:EJBModule=hello,J2EEApplication=null,J2EEServer=geronimo,j2eeType=StatelessSessionBean,name=Hello'started
> 
> cj
> 
> Aaron Mulder wrote:
> 
> >	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:
> >
> >  
> >
> 
> 

Mime
View raw message