Hi there,
I found the recent discussion on the mailing list about clean URLs
seemingly failing to find the right event handler when a form is POSTed,
and saw a variety of solutions to creating the URL oneself.
After trying to debug the same issue myself, I think the reason for this
behaviour is
Hi Nikolaos,
It probably is!
In my case, the only thing in my folder structure was JSPs, so moving
them to some other folder structure would fix the issue.
More generally, though, I thought that part of the magic of
DynamicMappingFilter was supposed to be that one could have one's action
beans
William,
I had a question, which i think is unrelated to your original problem:
Why are you using : @HandlesEvent() instead of renaming the
Resolution handler methods to the name you pass in param of
@HandlesEvent ?
ie:
public Resolution save() throws SchedulerException {
instead of:
Hi Sam,
Partly history -- I've used Stripes like that previously and hadn't looked into
the auto-mapping.
I had also wanted to be extra explicit to make sure that naming weirdness
wasn't why my events were not dispatched correctly.
And for the new event specifically, methods named new are not
