avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Hammant <Paul_Hamm...@yahoo.com>
Subject Re: how to "melt" phoenix with catalina
Date Tue, 27 Aug 2002 21:46:19 GMT

I dont quite understand your question.  However I'll answer it as it 
you'd asked "How do I go about componentizing Catalina so that it can 
run inside Phoenix as a set of blocks and present services to other 
Phoenix components".  Sorry if that is not what you are asking:

Basically , we tried and failed in previous months to mount Catalina as 
an interface/implementation separated set of components on top of 
Phoenix. We failed because of a couple of reasons - 1) there was poor 
interface/impl separation for Catalina itself.  And 2) some of the trees 
of class loaders would only work if they were mounted at root 
(primordial) level.    Things may have improved since then but we are 
mosting concentrating on Sevak which is a wrapper approach.  It still 
has problems though possibly related to (2) above.

- Paul

>I would like to ask you for help with the question 
>I've not found reply to yet. I'd like to build
>application server with various adapter frontends
>(read as thin as possible). The web adapter will
>go first.
>I've realized that the Avalon Phoenix and 
>Jakarta Tomcat are what I need start with.
>Now I'm trying to find hot to "melt" them 
>together. By melting I mean that there will
>be component(s) residing in Phoenix the JSP
>frontend will see in its scope(s). These
>components will provide both model and 
>controller functionality. I've looked
>at Sevak a bit and I don't see this ability 
>there. Can you please give me an advice what
>approach should I adopt ? I just like to know
>your opinions on where to make which interface,
>what extend etc. as I'm not able to get full 
>image at this time.
>Thank you for replies,

To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>

View raw message