Ulrich, > > I imagine that other components > > might require the ability to deploy web applications, create custom Service > > blocks within the web server, start/stop these service blocks, etc. > > Hmm... not sure about that one. Do we really want to write a management console > for Catalina? Also, it breaks IoC, doesn't it? Catalina already has a management console, we would simply be allowing clients to invoke without being tightly bound to Catalina. Breaks IoC...really?...how?
> > > For > > example, say that I have created a phoenix service that controls an external > > hardware resource and want to be able to manipulate that service via a web > > application. I would need to create a block that depends on Sevak and has > > the ability to specify a webapp Context that contains references back to > > itself, and to specify which Host within Sevak this webapp should be > > deployed to. > > You could do that with JMX much, much easier. You could do everything with JMX...no need for Avalon framework then...just look at JBoss! I would much rather program to compile-time checked interfaces that pass around ObjectNames any day. > > > Phoenix is an application server kernel...utilizing Phoenix as a component > > embedded within a Web Container does not make much sense. > > Catalina is also an application server kernel embedded within a Web Container. I disagree. Catalina is a Container that manages the lifecycle of Servlet instances. Phoenix is a Container that can manages the lifecycle of Avalon-based instances--who have a much richer set of lifecycle methods than Servlets. > > > If they won't componentize their design, we must create abstract wrappers to > > adapt the two. > > The problem I see is that we don't change anything semantically by writing > wrappers. You can wrap a GOTO statement in XML syntax, but it's still a GOTO. > Maybe I'm being overly pessimistic here :) Why do we need to change anything semantically? What is inheriantly wrong with the current state of Web Containers??? Far more reliable than GOTO statements! > > >>3) How about an ajpv12 or ajpv13 component? > > > You lost me here...what is the advantage? > > A Phoenix application can then act as backend to every webserver that supports > ajpv13 without the need for an intermittent Servlet Server. So this is going to > run on many platforms, not just a specific Servlet Server like Catalina. Plus, > it might be the easiest route, because the source code could be nicked from mod_jk. You want to rewrite the Servlet's API to Avalonize it? Could easily be done...but would always be a non-standard technology. > > > If you are looking for a way to provide web access via Sockets, I believe > > such components exist within Excalibur that can be used within Phoenix. > > Really? I couldn't find anything in the docs. Maybe in CVS? I checked...it is in the Cornerstone project...ConnectionManager and SocketManager components. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
