Daniel Fagerstrom schrieb:
Ralph Goers skrev:
Unfortunately, that will only let you share the session amongst
portlets in the same war. portlets in different wars, as well as
servlet filters running ahead of the portal won't have access to it.
For the blocks and servlet services we don't have this problem, all the
blocks are in the same war, shares the same global Spring container and
classloader. I would rather say that the problem in general for our
framework might rather be to little isolation. Neither the less we must
of course make the framework convenient to work with. I had some
suggestions about what to do when you need to share data between servlet
services in my previous post.
Not sure if it helps and don't know how it works, but you can share a
parent spring context between web apps. For sure, this might create
deployment problems in some environments where you can deploy wars only.
But perhaps it makes sense to further investigate there?
Carsten
