On Sun, Jun 22, 2008 at 1:46 PM, dusty <[EMAIL PROTECTED]> wrote: > In my UI I have things like <s:url/> and <s:form/> and <s:action/> that are > going to need to address resources. The routing system should make it easy > for me to both recognize incoming urls and to define rules for outbound url > html. Is the answer to create a custom tag library for <s:form/> that hides > the url details? or use a <s:url/> and reference that in <s:form>. I think > making the action param evaluate is moving in the wrong direction, making it > even more forced. A centralized REST routing system would be better so that > we can just reference it when we need to talk to resources.
What would this routing system look like? Ignore how Struts is designed today - how would you want such a system to work? How would you configure it? Don --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
