Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-615

Tapestry template parse should ignore the case of any Tapestry-specific elements (such as t:body, t:content, etc.)

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Trivial
    • Resolution: Fixed
    • 5.1.0.1
    • 5.1.0.3
    • tapestry-core
    • None

    Description

      Using <t:Body/> in a layout template throws the following error:

      Exception assembling root component of page home/Index: Unable to resolve 'Body' to a component class name. Available component types: ActionLink, AddRowLink, AjaxFormLoop, Any, BeanDisplay, BeanEditForm, BeanEditor, Checkbox, DateField, Delegate, Errors, EventLink, ExceptionDisplay, Form, FormFragment, FormInjector, Grid, GridCell, GridColumns, GridPager, GridRows, If, Label, Layout, LinkSubmit, Loop, Output, OutputRaw, PageLink, Palette, PasswordField, ProgressiveDisplay, PropertyDisplay, PropertyEditor, Radio, RadioGroup, RemoveRowLink, RenderObject, Select, Submit, SubmitNotifier, TextArea, TextField, TextOutput, Unless, Zone.

      Switch to <t:body/> and all is well.

      Component tags should be case-insensitive.

      Attachments

        Activity

          People

            hlship Howard Lewis Ship
            lutherbaker Luther Baker
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: