Hi folks,
I'm using DMF with a custom ActionResolver.
In MyActionResolver.getActionBeanType(String path), I need to access
ExecutionContext.getCurrentContext(), unfortunately it returns null.
The code in MyActionResolver goes like :
public Class<? extends ActionBean> getActionBeanType(String path) {
ActionBeanContext ctx =
ExecutionContext.currentContext().getActionBeanContext(); // throws
NPE
try {
ActionBean bean = getActionBean(ctx, path);
if (bean!=null) {
return bean.getClass();
}
return null;
} catch (StripesServletException e) {
return null;
}
}
As you see, it simply delegates to getActionBean(actionBeanContext,
path), so I use ExecutionContext.getCurrentContext() in order to
retrieve the current ActionBeanContext. I need to get the bean
context, as my action resolver is fully dynamic (action beans are not
known at startup time)... but I have this NPE.
I've investigated a bit, and I could see that the DMF calls
actionResolver before invoking the dispatcher, which is the one which
initializes the context :/
Using regular StripesFilter/Dispatcher web.xml config (without DMF),
or with MockRoundtrip, it works smoothly...
I'm kinda stuck, I don't want to hardcode those url mappings in web.xml... :/
Is there any way to get around this ?
Thanks in advance for any advice...
Cheers
Remi
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
