On 20.07.2010 18:10, Grégory Joseph wrote:
Hi Matteo,
It's something we've needed a few times, but somehow this hasn't made its way
to the codebase yet.
One approach would be to customize/patch MgnlServletContextListener to keep a
reference to it, as an attribute of the Magnolia SystemContext, for example.
But depending on the actual needs, you might be better using a "fake"
ServletContext to pass configuration values to the legacy code in question. (implement a
SC which wraps a Magnolia configuration node, for example)
HTH,
-g
Hi Grég,
yes, this have been our first approach, we are almost ready to go
through this way, but first we asked in list, obviously ;-)
I like the idea to wrap a Magnolia configuration node, good point! Maybe
something passed by scheduled job parameters.
Thanks, also to Ralf, mocking ServletContext is anyway a good idea.
Matteo
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
