[ 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.