> Also note the use of s:form's beanclass attribute instead of action, which
saves you from having to generate the URL in your ActionBean.
But then I have to manually add the params in all the jsps that use that
ActionBean, don't I? Is there a way to automate that or somehow condense
the added params into a custom tag? (Like I said, I'm new.) In my case it
seems it would be easier to have a single getUrl() method in a single
ActionBean than having to add the params with each s:form. Am I missing
something?
Also, the s:form action appealed to me because I can in the future bind a
new ActionBean to a part of the url if need be. For example, if the url
binding currently looks like
"/quest/{challengeName}/{toolName}/{questName}", I could later decide to
change the url bindings and use 2 separate ActionBeans to handle different
challenge names:
ActionBean1:
@UrlBinding("/quest/challenge1/{toolName}/{questName}/{$event}")
ActionBean2:
@UrlBinding("/quest/challenge2/{toolName}/{questName}/{$event}")
Peter
--
View this message in context:
http://www.nabble.com/form-action-embedded-parameters-tp22066427p22071994.html
Sent from the stripes-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
