[ http://issues.apache.org/jira/browse/TAPESTRY-538?page=comments#action_12318289 ]
Vjeran Marcinko commented on TAPESTRY-538: ------------------------------------------ I dunno if it is desirable for Tapestry to be responsible for Spring's startup/shutdown. I would like to leave to user to startup Spring in any desired way, prior to Tapestry, and thesedays it's most common by using : org.springframework.web.context.ContextLoaderListener inside web.xml, and Tapestry should internally just try to fetch specified bean using: WebApplicationContextUtils.getRequiredWebApplicationContext(ServletContext sc).getBean(...) and that's it! Right? > Provide basic, configurable Spring integration > ---------------------------------------------- > > Key: TAPESTRY-538 > URL: http://issues.apache.org/jira/browse/TAPESTRY-538 > Project: Tapestry > Type: New Feature > Components: Framework > Versions: 4.0 > Reporter: Howard M. Lewis Ship > > It would be very, very nice if these was basic Spring integration built into > Tapestry; enough to startup Spring and hook up the spring: object prefix. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
