imho the best way of doing this would be allowing the action parameter of the s:form tag to be evaluated (according to the S2 docs it currnetly isn't). That way people could use either <s:form action="/pet/%{id}" ....>...</s:form> or construct something like /pet/%{id}/delete using a URL object which is then handled by the existing rest code.

This would eliminate the need for any more tags, which i think would make things easier for others to get to grips with.

Al.

Jeromy Evans wrote:
Is there any interest in creating restful form tags?

I've created variations of the s:form tag (create, destroy, index, update) that simply and/or enforce the restful conventions. Basically, the action attribute of s:form is removed and replaced with a resourceURI attribute that understands the convention and context. eg. a create tag knows that if the current uri ends with "/pet/editNew" then the target URI is "/pet" (and the resourceURI attribute doesn't need to be specified).

I've found them a useful simplification. Eventually the s:action tag also needs to be substituted with one that knows which method to invoke based on the current context.

I don't think these belong in the rest plugin as we eventually want to achieve independence of the tag implementation though.

Any interest?  If not I may just push them onto googlecode.

cheers,
Jeromy Evans

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to