So I did get it working, by overriding getActionBean in NameBasedActionResolver.
However I'm still stuck with something I dislike. I'm following the pattern as described in 'Binding Into Domain Models' so when I receive a request for /SomeClass.action while SomeClassActionBean does not exist, it will instantiate SuperClassActionBean. The problem arises in the .jsp where I refer to the actionBean like so:

<stripes:useActionBean binding="/SomeClass.action" var="actionBean" />

by default, however, Stripes does not find the actionBean I created in the overridden method getActionBean. In order for Stripes to find it, I had to put the actionBean into a request attribute by going request.setAttribute("/SomeClass.action", newInstanceOfSuperClassActionBean). This I could only find out by inspecting the Stripes sources. Is there a better way to trick Stripes into reusing the SuperClassActionBean?


De: [] En nombre de Willem Vermeer
Enviado el: miércoles, 07 de febrero de 2007 10:59
Para: Stripes Users List
Asunto: [Stripes-users] ActionBean resolution

Hi all,
Can somebody help me out with the following:
I have a bunch of classes with CRUD-jsp's. I created one super ActionBean class say SuperActionBean. Some of my classes require specific handling in their own SomeClassActionBean (=subclass of SuperActionBean) but most of them only require the default processing done in SuperActionBean.
How do I configure Stripes such that, whenever it receives a request for /SomeClass.action and subsequently finds out that SomeClassActionBean does not exist, in that case it should instantiate SuperActionBean?
I have been fiddling around with a subclass of NameBasedActionResolver overriding handleActionBeanNotFound or getActionBean(context, string) but to no avail.