So one way it could be done is with a service with the various interceptors, but then there is the issue of how the deployers/aspects integrate with it. The aop framework already has a similar notion, what I'm struggling with is that the starting point for accessing an interface like this:
| interface ScopedMetaData
| Object getData(Scope scope, Object key);
| vois setData(Scope scope, Object key, Object data);
or are there other factilities to chain together maps? Think about two invocations, one to access an attribute on an SFSB container and a second SFSB method invocation on a bean in the container. The first has no session scope data context, the second does, but also has a different and overriding request scope data context.
Now back to the original problem of scoped PropertyEditors. One way to implement this is by updating the PropertyEditorsMgr to have aspects which look for registered entries at the various scopes. This is an example where I don't expect any explicit use of the scope during the lookup. Can we explore a prototype of this to make this discussion more concrete?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3898845#3898845
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3898845