DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21853>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21853 [patch][woody] Making WoodyTemplateTransformer Flow-aware. Summary: [patch][woody] Making WoodyTemplateTransformer Flow- aware. Product: Cocoon 2 Version: Current CVS 2.1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: general components AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] This patch allows 1/ to have the form/@action dynamically set to a jxpath evalutaion of the form #{$continuation/id} 2/ to look for the form instance in the flow context model -- This introduces a jxpath context member in the template transformer that is used for evaluating #{--jxpath-expression--} in the text of a wt:form-template tag Typical usage is in updating your existing woody-templates to hold this tag: <wt:form-template method="POST" action="#{$continuation/id}.kont"> -- This also lowers the required 'form-attribute' parameter to be an optional parameter. If it is not set then the flow-context-object will be considered being a java.util.Map that holds the form instance under the 'woody-form' key -- Finally this holds some comments/suggestion about how we could extend this even one step further to actually support multiple woody-forms on one page. We could allow for multiple wt:form-template tags on one page that each declare themselves the form-lookup key in the flow-context-object-HashMap using their own specific @location="#{/woody-form}" -marc=