Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6842043
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T00:02:57+00:00 2026-05-27T00:02:57+00:00

in tapestry we can use the component in two ways <t:type=grid t:source=persons t:row=person t:encoder=personEncoder

  • 0

in tapestry we can use the component in two ways

<t:type="grid" t:source="persons" t:row="person" t:encoder="personEncoder" t:include="id,firstname,lastname,startdate" t:add="delete"\>

or we can use

<t:grid source="persons" row="person" encoder="personEncoder" include="id,firstname,lastname,startdate" add="delete"></t:grid>

So my question is that is there any difference or specific reason to use the components in two different way?

Regards,
Mahendra Athneria

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-27T00:02:58+00:00Added an answer on May 27, 2026 at 12:02 am

    Does the first one really work? I think you mean

    <table t:type="grid" ... />
    

    vs.

    <t:grid ... />
    

    If so, there is no functional difference. I always prefer using the first style because it looks like proper HTML with instrumentation instructions for Tapestry, rather than just a bunch of Tapestry-specific tags.

    The t: prefix for component parameters refers to the Tapestry namespace and is the clean way to define value bindings. Both styles will work with either t: present or omitted, as it is optional in most places, except in the odd case when it is not. (For example, you’ll sometimes want both id and t:id on Zone components, and they’ll actually mean different things.)

    TL;DR: Use the <table t:type="grid" t:source="" ... /> style.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I want to use an EJB3 from within my Tapestry Page class, I can
Apache Wicket ( http://wicket.apache.org/ ) and Apache Tapestry ( http://wicket.apache.org/ ) are both component
I use Tapestry 4, and whenever we push a release that changes any assets
Can we declare/create inner class in Tapestry page and access it to the corresponding
Can any one explain me the difference between Struts and Tapestry framework or may
I am facing one problem in Tapestry. Problem - I am using a grid
If you're using a component-based (aka Pull-based ) web framework (e.g. Tapestry, Wicket, et
I'm facing a problem when using tapestry 5.2.0 : using multiple times a component
I am updating the tapestry version from 5.0.18 to 5.2.6. How can I disable
I have a Tapestry application that is serving its page as UTF-8. That is,

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.