[
http://jira.magnolia-cms.com/browse/MAGNOLIA-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Mattsson updated MAGNOLIA-3376:
--------------------------------------
Description:
Currently the ServletContext is not available to modules during startup. This
is for instance a problem in integration scenarios where the module starts a
framework such as Spring. In blossom this has been solved by adding an extra
context listener. A cleaner solution would be to make it available in standard
magnolia.
Modules are started using SystemContext. Set in ConfigLoader.load() or
ModuleManagerWebUI.execute().
If we add getServletContext() to SystemContext it still has to be taken from
somewhere. The implementation we use for SystemContext is configured in
mgnl-beans.properties and created by Components. The implementation would have
to look for it somewhere, probably a static field.
If we had a DI container in place then ServletContext could have been one of
the injectible types and the problem would be solved.
was:
Currently the ServletContext is not available to modules during startup. This
is for instance a problem in integration scenarios where the module starts a
framework such as Spring. In blossom this has been solved by adding an extra
context listener. A cleaner solution would be to make it available in standard
magnolia.
Modules are started using SystemContext. Set in ConfigLoader.load() or
ModuleManagerWebUI.execute().
If we add getServletContext() to SystemContext it still has to be taken from
somewhere. The implementation we use for SystemContext is configured in
mgnl-beans.properties and created by Components. The implementation would have
to look for it somewhere, probably a static field.
If we had a DI container in place then ServletContext could have been of of the
injectible types and the problem would be solved.
> ServletContext should be available to modules during startup
> ------------------------------------------------------------
>
> Key: MAGNOLIA-3376
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3376
> Project: Magnolia
> Issue Type: Improvement
> Components: modulemechanism
> Reporter: Tobias Mattsson
> Assignee: Tobias Mattsson
>
> Currently the ServletContext is not available to modules during startup. This
> is for instance a problem in integration scenarios where the module starts a
> framework such as Spring. In blossom this has been solved by adding an extra
> context listener. A cleaner solution would be to make it available in
> standard magnolia.
> Modules are started using SystemContext. Set in ConfigLoader.load() or
> ModuleManagerWebUI.execute().
> If we add getServletContext() to SystemContext it still has to be taken from
> somewhere. The implementation we use for SystemContext is configured in
> mgnl-beans.properties and created by Components. The implementation would
> have to look for it somewhere, probably a static field.
> If we had a DI container in place then ServletContext could have been one of
> the injectible types and the problem would be solved.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
