[ http://issues.apache.org/jira/browse/TAPESTRY-717?page=comments#action_12459851 ] Norbert Sándor commented on TAPESTRY-717: -----------------------------------------
I agree with Navin. Besides in more complex applications I often find it necessary to access hivemind services from POJOs. There is a related hivemind issue as well: http://issues.apache.org/jira/browse/HIVEMIND-179 > Easier accessing the hivemind registry > -------------------------------------- > > Key: TAPESTRY-717 > URL: http://issues.apache.org/jira/browse/TAPESTRY-717 > Project: Tapestry > Issue Type: Improvement > Components: Framework > Affects Versions: 4.0 > Reporter: Ron Piterman > Assigned To: Jesse Kuhnert > Fix For: 4.1.2 > > > Currently, the servlet stores the hivemind registry in the content, but > provides no easy way of obtaining access to it. Both the prefix and the > _registry members are private, so one must hack in order to access it ( by > hack I also mean just copying the registry prefix to another visible static > member). > This is also a J2EE compatibility issue. > If one wishes to integrate Tapestry with other features, the hivemind > registry is essential. > Currently I stumble on a SessionListener, which needs to do some cleanu, and > depends on ASOs and Hivemind (custom) services to do so. > wouldn't it be possible to "publish" the registry using JNDI ? -- 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]
