Ken,
I've had this type of problem before too. In the situation you're
describing, usually cleaning the project will fix it for me. Sometimes
the IDE or Tomcat leaves garbage classes around especially when
refactoring and those classes may conflict with your new code.
Here's some other similar problems I've experienced:
Because of the way Stripes uses parameter names to determine the event
you will cause problems if you try to map fields with the same name as
an event.
If you've got a directory you're trying to serve files from - we'll call
it "/test/" - and then you add @URLBinding("/test") to one of your
action beans either your resources in the directory or your action bean
will be unavailable due to mapping conflicts.
Often when I run into one of these problems I'll try to debug with the
HTTP info available in firebug or I'll break out Wireshark and sniff the
HTTP packets.
Aaron
Ken Barnes wrote:
> I have been using stripes for about 2 years now and have finally run into this
> problem enough to post. Sometimes randomly my stripes bean will not handle
> submit event from the jsp and always goes right to the default handler. I
> have
> avoided this by simply creating another project and copying/pasting and
> somehow
> it handles the events again. I have also tried adding @HandlesEvent("") to
> each
> resolution method but that does nothing. Has anyone ever experienced this as
> this is my fifth time or so. Is there a magic trigger or spelling of tag
> names
> that causes the bean to only hit default>>>>??
> Thanks
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Stripes-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/stripes-users
>
>
------------------------------------------------------------------------------
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
