[Prev] Thread [Next]  |  [Prev] Date [Next]

[jira] Commented: (TAPESTRY-717) Easier accessing the hivemind registry Jesse Kuhnert (JIRA) Tue Dec 19 18:06:15 2006

Jesse Kuhnert commented on TAPESTRY-717:

I think I'd first like to know what problems are being solved by making the 
registry easier to get access to. 

I believe this is currently actually done on purpose, ie "by design". I really 
doubt there is anything you need to do that couldn't/shouldn't be done using 
built-in hivemind service capabilities but I'm open to suggestion. 

Closing this out for now but will happily re-open if anyone cares enough to 
throw in some more thoughts.

> 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
>             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: 
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]