You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Massimo Lusetti (JIRA)" <ji...@apache.org> on 2010/01/17 23:36:54 UTC
[jira] Created: (TAP5-988) Store the Registry into the
ServletContext after is has performed registry startup
Store the Registry into the ServletContext after is has performed registry startup
----------------------------------------------------------------------------------
Key: TAP5-988
URL: https://issues.apache.org/jira/browse/TAP5-988
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.2.0, 5.2
Reporter: Massimo Lusetti
Attachments: patch.p0
The Registry is stored in the ServletContext just after it's creation before calling "performRegistryStartup".
This could cause trouble if anyone would like to access the Registry from a listener (ex ServletContextListener)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TAP5-988) Store the Registry into the
ServletContext after is has performed registry startup
Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Drobiazko reassigned TAP5-988:
-----------------------------------
Assignee: Igor Drobiazko
> Store the Registry into the ServletContext after is has performed registry startup
> ----------------------------------------------------------------------------------
>
> Key: TAP5-988
> URL: https://issues.apache.org/jira/browse/TAP5-988
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.2.0, 5.2
> Reporter: Massimo Lusetti
> Assignee: Igor Drobiazko
> Attachments: patch.p0
>
>
> The Registry is stored in the ServletContext just after it's creation before calling "performRegistryStartup".
> This could cause trouble if anyone would like to access the Registry from a listener (ex ServletContextListener)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-988) Store the Registry into the
ServletContext after is has performed registry startup
Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Drobiazko closed TAP5-988.
-------------------------------
Resolution: Won't Fix
The patch breaks the spring integration. Spring initialization relies that registry is available in ServletContext and is performed in the ApplicationInitializer pipeline. The patch stores the registry into ServletContext after ApplicationInitializer pipeline is invoked. This causes an error when ApplicationContext creation is invoked. Feel free to reopen the issue if this is a critical issue for you.
> Store the Registry into the ServletContext after is has performed registry startup
> ----------------------------------------------------------------------------------
>
> Key: TAP5-988
> URL: https://issues.apache.org/jira/browse/TAP5-988
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.2.0, 5.2
> Reporter: Massimo Lusetti
> Assignee: Igor Drobiazko
> Attachments: patch.p0
>
>
> The Registry is stored in the ServletContext just after it's creation before calling "performRegistryStartup".
> This could cause trouble if anyone would like to access the Registry from a listener (ex ServletContextListener)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-988) Store the Registry into the
ServletContext after is has performed registry startup
Posted by "Massimo Lusetti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Massimo Lusetti updated TAP5-988:
---------------------------------
Attachment: patch.p0
simple patch to postpone the operation
> Store the Registry into the ServletContext after is has performed registry startup
> ----------------------------------------------------------------------------------
>
> Key: TAP5-988
> URL: https://issues.apache.org/jira/browse/TAP5-988
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.2.0, 5.2
> Reporter: Massimo Lusetti
> Attachments: patch.p0
>
>
> The Registry is stored in the ServletContext just after it's creation before calling "performRegistryStartup".
> This could cause trouble if anyone would like to access the Registry from a listener (ex ServletContextListener)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TAP5-988) Store the Registry into the
ServletContext after is has performed registry startup
Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Drobiazko reassigned TAP5-988:
-----------------------------------
Assignee: Igor Drobiazko
> Store the Registry into the ServletContext after is has performed registry startup
> ----------------------------------------------------------------------------------
>
> Key: TAP5-988
> URL: https://issues.apache.org/jira/browse/TAP5-988
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.2.0, 5.2
> Reporter: Massimo Lusetti
> Assignee: Igor Drobiazko
> Attachments: patch.p0
>
>
> The Registry is stored in the ServletContext just after it's creation before calling "performRegistryStartup".
> This could cause trouble if anyone would like to access the Registry from a listener (ex ServletContextListener)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-988) Store the Registry into the
ServletContext after is has performed registry startup
Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Drobiazko closed TAP5-988.
-------------------------------
Resolution: Won't Fix
The patch breaks the spring integration. Spring initialization relies that registry is available in ServletContext and is performed in the ApplicationInitializer pipeline. The patch stores the registry into ServletContext after ApplicationInitializer pipeline is invoked. This causes an error when ApplicationContext creation is invoked. Feel free to reopen the issue if this is a critical issue for you.
> Store the Registry into the ServletContext after is has performed registry startup
> ----------------------------------------------------------------------------------
>
> Key: TAP5-988
> URL: https://issues.apache.org/jira/browse/TAP5-988
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.2.0, 5.2
> Reporter: Massimo Lusetti
> Assignee: Igor Drobiazko
> Attachments: patch.p0
>
>
> The Registry is stored in the ServletContext just after it's creation before calling "performRegistryStartup".
> This could cause trouble if anyone would like to access the Registry from a listener (ex ServletContextListener)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-988) Store the Registry into the
ServletContext after is has performed registry startup
Posted by "Massimo Lusetti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Massimo Lusetti updated TAP5-988:
---------------------------------
Attachment: patch.p0
simple patch to postpone the operation
> Store the Registry into the ServletContext after is has performed registry startup
> ----------------------------------------------------------------------------------
>
> Key: TAP5-988
> URL: https://issues.apache.org/jira/browse/TAP5-988
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.2.0, 5.2
> Reporter: Massimo Lusetti
> Attachments: patch.p0
>
>
> The Registry is stored in the ServletContext just after it's creation before calling "performRegistryStartup".
> This could cause trouble if anyone would like to access the Registry from a listener (ex ServletContextListener)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.