Andrew Stevens skrev:
Date: Wed, 18 Jul 2007 23:42:34 -0400
From: [EMAIL PROTECTED]
With the current servlet service framework I just don't know how to
integrate JSPs - what this thread was actually about.
Isn't the standard way of integrating JSP to just call it through a
Joerg Heinicke skrev:
On 17.07.2007 06:08, Daniel Fagerstrom wrote:
Ok, sorry for implying that. The only alternative is probably to use
the shared application context as mentioned in the thread about
interblock communication [1].
I guess that would mean that each Cocoon block should be a
Date: Wed, 18 Jul 2007 23:42:34 -0400
From: [EMAIL PROTECTED]
With the current servlet service framework I just don't know how to
integrate JSPs - what this thread was actually about.
Isn't the standard way of integrating JSP to just call it through a
RequestDispatcher that you
On 17.07.2007 06:08, Daniel Fagerstrom wrote:
Ok, sorry for implying that. The only alternative is probably to use
the shared application context as mentioned in the thread about
interblock communication [1].
I guess that would mean that each Cocoon block should be a war and have
its own
Joerg Heinicke skrev:
On 16.07.2007 04:32, Daniel Fagerstrom wrote:
From what I understand other servlets need to be registered in Cocoon
(or the underlying Spring container). Doesn't that make it
a servlet container in a servlet container?
Yes, but the internal container is very light
Joerg Heinicke skrev:
...
From what I understand other servlets need to be
registered in Cocoon (or the underlying Spring container). Doesn't that make it
a servlet container in a servlet container?
Yes, but the internal container is very light weight.
This approach still seems to suffer
from
On 16.07.2007 04:32, Daniel Fagerstrom wrote:
From what I understand other servlets need to be registered in Cocoon
(or the underlying Spring container). Doesn't that make it
a servlet container in a servlet container?
Yes, but the internal container is very light weight.
So I would say
On 12.07.2007 05:31, Grzegorz Kossakowski wrote:
Basically, you need to register JSP servlet as Spring bean, then you can
connect to it from other servlet (Cocoon block) using its bean's Id and use
servlet:/ source for this.
All needed functionality is already there and working, it's a
Joerg Heinicke pisze:
On 12.07.2007 05:31, Grzegorz Kossakowski wrote:
How is that supposed to work with JSPs where Jasper (when using Tomcat) needs to
kick in and compile the JSPs? From what I understand other servlets need to be
registered in Cocoon (or the underlying Spring container).
Reposted, since I didn't get a copy from the list and don't see it in the
archives. Apologies if you've seen it already.
Date: Thu, 12 Jul 2007 11:31:51 +0200
From: [EMAIL PROTECTED]
Joerg Heinicke pisze:
On 02.07.2007 20:19, Andrew Stevens wrote:
And then inspiration hit - why not
On 13.07.2007 16:58, Grzegorz Kossakowski wrote:
I really have no experience with JSP and I don't know how its servlet is
initialized and how it works. If you could explain what could be a
possible problem I would try to answer according to my knowledge.
Me neither. My last project was the
On 13.07.2007 20:38, Andrew Stevens wrote:
In our existing 2.1.x app, I got it working by creating a new
JSPEngine implementation that looks up the RequestDispatcher for the
supplied URL and calls include or forward directly on that (instead
of using JSPEngineImplNamedDispatcherInclude to look
Joerg Heinicke pisze:
On 02.07.2007 20:19, Andrew Stevens wrote:
And then inspiration hit - why not instead create a new input Source
for JSPs?
And then I started to over-think it :-) Why only JSPs? Why not
servlets too? How does this differ from the context: source type?
Surely someone
On 02.07.2007 20:19, Andrew Stevens wrote:
And then inspiration hit - why not instead create a new input Source
for JSPs?
And then I started to over-think it :-) Why only JSPs? Why not
servlets too? How does this differ from the context: source type?
Surely someone must have thought of
14 matches
Mail list logo
