You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by bu...@apache.org on 2003/08/01 14:12:56 UTC

DO NOT REPLY [Bug 22049] New: - Allow template parser to support jwcid which declares both component and content

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=22049>.
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=22049

Allow template parser to support jwcid which declares both component and content

           Summary: Allow template parser to support jwcid which declares
                    both component and content
           Product: Tapestry
           Version: 3.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Framework
        AssignedTo: tapestry-dev@jakarta.apache.org
        ReportedBy: colinml1@exis.com


As per discussion on the mailing list on 2003-7-31, it would be desirable for
the template parser to support jwcid declarations in a form similar to
  <body jwcid="@Body,$content$"> ... </body>

This would be equivalent to 
  <span jwcid="$content$">
  <body jwcid="@Body">
  ...
  </body>
  </span>

but has the advantage that it is conformant html (notwithstanding the non-html
jwcid attribute of course), while the longer form is non-conformant, since spans
are not allowed outside of a body element.

There are currently a number of samples and examples in Tapestry which do use
spans outside of the body. While there are a few other ways to structure the
html, non of them are as clean or concise as this enhancement would allow.