Hi Bob,

you have to use <t:parameter name="nameCell"> instead of <t:parameter
name="name">.

Christoph

Heck, Bob wrote:
> Yes, Thing has a property of name. Not using a custom model.  Tapestry
> sees the Thing and knows it has 'Name' and 'Size' columns, because it
> constructs the grid with those column headers and puts the correct
> values in each column.  I just want to tell it to put a link in the
> 'Name' column.  That is all.  Seems ever so simple.  But, although it
> knows that Thing has a name property, it is ignoring the <t:parameter
> name="name"> tag.  I have even tried taking out the pagelink tag and
> putting in alternative text.  The <t:parameter name="name"> tag is
> completely ignored still.
> 
>  
> 
> -----Original Message-----
> From: Jonathan Barker [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, October 17, 2007 14:53
> To: 'Tapestry users'
> Subject: RE: Using row param in grid
> 
> 
> I assume you have a column for the "name" property of Thing.  Then you
> want your parameter to be for <t:parameter name="nameCell">
> 
> 
>> -----Original Message-----
>> From: Heck, Bob [mailto:[EMAIL PROTECTED]
>> Sent: Wednesday, October 17, 2007 3:22 PM
>> To: Tapestry users
>> Subject: RE: Using row param in grid
>>
>> Ok, thanks for that.  Added property to page to store Thing.  No more 
>> error, but, now it seems as if the page is being rendered without 
>> regard to the <t:parameter> tag.  It is completely ignored and the 
>> grid is rendered as if the parameter tag is not even there, in other 
>> words, no link is created.  View source, just standard table and text,
> 
>> no link tag.
>>
>> Thanks for your help in advance.
>>
>>
>>
>> -----Original Message-----
>> From: Davor Hrg [mailto:[EMAIL PROTECTED]
>> Sent: Wednesday, October 17, 2007 13:53
>> To: Tapestry users
>> Subject: Re: Using row param in grid
>>
>> you must create a property to store current row (for example "thing") 
>> getThing and setThing ..
>>
>> and change your template:
>>
>> <t:grid t:source="thingList" row="thing">
>>        <t:parameter name="name">
>>                <t:pagelink page="Start"
>> context="Thing.name">${thing.name}</t:pagelink>
>>        </t:parameter>
>> </t:grid>
>>
>>
>> the concept here is that you give list of objects to grid with source=
> 
>> from which grid reads data for the loop.
>> but the row=  tells the grid where you want to store the current value
> 
>> which is where grid writes data.
>>
>> I'm not explaining this very well, but "binding" is a basic tapestry 
>> concept.
>>
>> Davor Hrg
>>
>>
>> On 10/17/07, Heck, Bob <[EMAIL PROTECTED]> wrote:
>>> I have a .page that returns a List<Thing>  - that works.
>>>
>>>
>>>
>>> When I try this:
>>>
>>> <t:grid t:source="thingList" row="Thing">
>>>         <t:parameter name="name">
>>>                 <t:pagelink page="Start"
>>> context="Thing.name">${Thing.name}</t:pagelink>
>>>         </t:parameter>
>>> </t:grid>
>>>
>>> I get this:
>>>
>>> ---
>>> org.apache.tapestry.ioc.internal.util.TapestryException
>>>
>>> Could not convert 'Thing.name' into a component parameter binding:
>>> Class eds.sla.spring.web.tapestry.pages.DocManagement does not 
>>> contain
>>> a property named 'Thing' (within property expression 'Thing.name').
>>> Available properties: class, componentResources, thingList.
>>> ---
>>>
>>> thingList is a List<Thing> and is populated.
>>>
>>> the getThingList() on the page works and returns the List<Thing>.  
>>> So,
>>> why can't tapestry see Thing?  Thing is the row, it is the type of 
>>> object that is returned in the List.
>>>
>>>
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> 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]
> 
> 
> ---------------------------------------------------------------------
> 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