On 18/09/2012 23:57, Thorsten Scherler wrote:
Hi all,
I am working on COCOON3-105 whenever I find a sec, but I am thinking
about the underlying problem for a while now.
Hi Thorsten,
I don't know how much useful can be my contribution in this field,
anyway here are my 2 cents.
To resume,
On 19/09/2012 09:14, Francesco Chicchiriccò wrote:
[...]
Indeed, I think this is the route to follow, i.e. move the
blockContexts Map in a place bound to app scope, not to JVM scope
(like as BlockContextURLStreamHandlerFactory).
What if you get to the servletContext not via
ServletContext
On 09/19/2012 03:17 PM, Francesco Chicchiriccò wrote:
Anyway, what if we try to use cocoon-jnet [2] for handling
blockcontext:// ? AFAIK it is only used for servlet:// ATM.
JNet was my first thought too ...
--
Reinhard Pötz Founder Managing Director, Indoqa and Deepsearch
