You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Paul Russell <pa...@luminas.co.uk> on 2000/12/04 13:32:30 UTC
Re: Will cocoon2 be a servlet?
On Mon, Dec 04, 2000 at 12:55:43PM +0000, Ulrich Mayring wrote:
> looking at the Avalon framework it seems it doesn't support servlets, is
> that correct? Will taglibs that use the servlet API not work under
> cocoon2 because of that?
There are mumblings inside Avalon towers about an api for
managing this hierachic relationships -- it's called Camelot,
and it's described as a containment API. It should allow us to
put a servlet container inside avalon in a uniform fashion,
and therefore cocoon2 could live inside that (remember that
cocoon2 is still a servlet at present). Alternatively, we could
move Cocoon2 over to being a service within avalon, although
I'm not sure if the service cocoon provides is general enough
to be imeplemented elsewhere. What are you doing that requires
the servlet api? There may well be an alternative even if we
did move over to being a service.
--
Paul Russell <pa...@luminas.co.uk>
Technical Director, http://www.luminas.co.uk
Luminas Ltd.
Re: Will cocoon2 be a servlet?
Posted by Paul Russell <pa...@luminas.co.uk>.
On Mon, Dec 04, 2000 at 07:45:20PM +0000, Ulrich Mayring wrote:
> Paul Russell wrote:
> > There are mumblings inside Avalon towers about an api for
> > managing this hierachic relationships -- it's called Camelot,
> > and it's described as a containment API. It should allow us to
> > put a servlet container inside avalon in a uniform fashion,
> > and therefore cocoon2 could live inside that (remember that
> > cocoon2 is still a servlet at present). Alternatively, we could
> > move Cocoon2 over to being a service within avalon, although
> > I'm not sure if the service cocoon provides is general enough
> > to be imeplemented elsewhere. What are you doing that requires
> > the servlet api? There may well be an alternative even if we
> > did move over to being a service.
> Well, what about the Response object, the Request object, the Session
> object, ....
Most of that *should* be generalised, I'd have thought? Having
said that, I've just noticed that CommandLineRequest is derived
from HttpServletRequest. Should there be generic request and
response interfaces?
Paul.
cc Cocoon-dev for some further perusal.
--
Paul Russell <pa...@luminas.co.uk>
Technical Director, http://www.luminas.co.uk
Luminas Ltd.
Re: Will cocoon2 be a servlet?
Posted by Paul Russell <pa...@luminas.co.uk>.
On Mon, Dec 04, 2000 at 07:45:20PM +0000, Ulrich Mayring wrote:
> Paul Russell wrote:
> > There are mumblings inside Avalon towers about an api for
> > managing this hierachic relationships -- it's called Camelot,
> > and it's described as a containment API. It should allow us to
> > put a servlet container inside avalon in a uniform fashion,
> > and therefore cocoon2 could live inside that (remember that
> > cocoon2 is still a servlet at present). Alternatively, we could
> > move Cocoon2 over to being a service within avalon, although
> > I'm not sure if the service cocoon provides is general enough
> > to be imeplemented elsewhere. What are you doing that requires
> > the servlet api? There may well be an alternative even if we
> > did move over to being a service.
> Well, what about the Response object, the Request object, the Session
> object, ....
Most of that *should* be generalised, I'd have thought? Having
said that, I've just noticed that CommandLineRequest is derived
from HttpServletRequest. Should there be generic request and
response interfaces?
Paul.
cc Cocoon-dev for some further perusal.
--
Paul Russell <pa...@luminas.co.uk>
Technical Director, http://www.luminas.co.uk
Luminas Ltd.
Re: Will cocoon2 be a servlet?
Posted by Ulrich Mayring <ul...@denic.de>.
Paul Russell wrote:
>
> On Mon, Dec 04, 2000 at 12:55:43PM +0000, Ulrich Mayring wrote:
> > looking at the Avalon framework it seems it doesn't support servlets, is
> > that correct? Will taglibs that use the servlet API not work under
> > cocoon2 because of that?
>
> There are mumblings inside Avalon towers about an api for
> managing this hierachic relationships -- it's called Camelot,
> and it's described as a containment API. It should allow us to
> put a servlet container inside avalon in a uniform fashion,
> and therefore cocoon2 could live inside that (remember that
> cocoon2 is still a servlet at present). Alternatively, we could
> move Cocoon2 over to being a service within avalon, although
> I'm not sure if the service cocoon provides is general enough
> to be imeplemented elsewhere. What are you doing that requires
> the servlet api? There may well be an alternative even if we
> did move over to being a service.
Well, what about the Response object, the Request object, the Session
object, ....
Ulrich
--
Ulrich Mayring
DENIC eG, Systementwicklung