I don't understand why you say action="/foo" does not work. That is the
base path to which the ActionBean is bound so it will be dispatched
correctly, and all the form inputs will be available as parameters just
as they normally would. I don't see any advantage to supporting clean
URLs on a form submission.
Kai Grabfelder wrote:
> Hi there,
>
> there is a problem with the current imlementation of the Clean URLs stuff in
> the
> trunk: Think of the following url binding in an action Bean
>
> @UrlBinding(value = "/foo/{id}/index.htm")
> MyActionBean implements ActionBean
>
> Now the following stripes form tag
> <stripes:form beanclass="MyActionBean ">
>
> produces the following output:
> <form action="/foo" method="post">
>
> which obviously does not work. Workaround would be to not use the beanclass
> attribute which would be quite inconsitent to the way stripes works.
>
> Any ideas how we could solve this?
>
> Maybe the stripes:form tag should support the param:tag (like the <link:tag>
> does)? I guess this would be the most consistent solution. What do you think?
>
> regards
>
> Kai
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Stripes-development mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/stripes-development
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
