My view is that scope is an aspect that should not be explicitly encoded in an
application. We need the jboss microcontainer metdata repository notion
(http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss5RepositoryClasses,
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=73653) woven
throughout the jboss layers.
The potential point of conflict is whether use of a standard legacy accessor
like HttpServletRequest.getParameter("user.home") should suddenly be treated as
a heirarchical variable that can be overriden by an thread local aspect, as
well as have a default value coming from less dynamic scopes (deployment
configuration, system property, server defaults, admin domain defaults, etc.).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3925134#3925134
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3925134
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
