From Merlin 2.0
[INFO ] (root.sevak): Sevak.contextualize() [INFO ] (root.sevak): Sevak.service() [INFO ] (root.sevak): Sevak.initialize() Apache Tomcat/4.1.7 Jul 24, 2002 3:40:54 AM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Jul 24, 2002 3:40:54 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 [INFO ] (root): started: service:/root/sevak [DEBUG ] (root): started [INFO ] (root): container startup complete [DEBUG ] (root): shutdown [DEBUG ] (root): stop [DEBUG ] (root): stopped [INFO ] (root): container shutdown complete Cheers, Steve. Jason van Zyl wrote: >Hi, > >Is there any reason in particular things like Sevak go into Phoenix and >aren't just normal components? I want a servlet container component but >I'm not running phoenix. Looking at it I could easily strip out phoenix >references and make it work in fortress or my tweety mutant. > >Is there any reason there couldn't be phoenix wrappers for things like >Sevak. Sevak in particular seems out of place because as something like >Sevak might be assembled into something larger to form an application >but isn't an application itself. > >Will the common metadata/containerkit work allow for there to be more >standard components? > > > -- Stephen J. McConnell OSM SARL digital products for a global economy mailto:[EMAIL PROTECTED] http://www.osm.net -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
