You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Steven Woolley <wo...@gmail.com> on 2008/04/28 04:22:46 UTC

actionlink and pagelink id's no longer (automatically) rendered in 5.0.12-snapshot

Upgrading from 5.0.6 to the latest snapshot, I found that all my  
pagelinks and actionlinks defined in tml like this:

<a t:id="blah" t:type="actionlink" >link</a>

re no longer rendering with the clientid, ie.:

<a src="page.blah" id="blah">link</a>

Instead, I get no id...

Same thing goes for pagelinks...

I can force the id to be rendered with:
<a t:id="blah" id="blah" t:type="actionlink" >link</a>

but, that's kinda annoying, and if I render them in a loop, I no  
longer get unique id's for each link....

Am I missing something?  Is this a bug, or the way things will be in  
the future?
Thanks,
Steve

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: actionlink and pagelink id's no longer (automatically) rendered in 5.0.12-snapshot

Posted by Steven Woolley <wo...@gmail.com>.
Something's fishy then...

I just double checked, very latest snapshot from maven:

http://tapestry.formos.com/maven-snapshot-repository//org/apache/ 
tapestry/tapestry-core/5.0.12-SNAPSHOT/tapestry- 
core-5.0.12-20080428.110035-48.jar

Test.java:
package org.example.myapp.pages;

public class Test {

}

Test.tml:
<html xmlns:t="http://tapestry.apache.org/schema/tapestry_5_0_0.xsd">
     <head><title>test</title></head>
     <body>
     <a t:id="addSongsToList" t:type="actionlink" ></a>
     </body>
</html>

renders:
<html><head><link href="assets/tapestry/5.0.12-SNAPSHOT/default.css"  
rel="stylesheet" type="text/css"><title>test</title></head><body><a  
href="test.addsongstolist"></a></body></html>

Same thing in a loop renders:

<html><head><link href="assets/tapestry/5.0.12-SNAPSHOT/default.css"  
rel="stylesheet" type="text/css"><title>test</title></head><body><a  
href="test.addsongstolist"></a><a href="test.addsongstolist"></a><a  
href="test.addsongstolist"></a></body></html>

And if I explicitly set the id="something":
<html><head><link href="assets/tapestry/5.0.12-SNAPSHOT/default.css"  
rel="stylesheet" type="text/css"><title>test</title></head><body><a  
href="test.addsongstolist" id="something"></a><a  
href="test.addsongstolist" id="something"></a><a  
href="test.addsongstolist" id="something"></a></body></html>

Also double checked in 5.0.11 and it works as expected:
Test.tml:
<html xmlns:t="http://tapestry.apache.org/schema/tapestry_5_0_0.xsd">
     <head><title>test</title></head>
     <body>
     <t:loop source="1..3">
     	<a t:id="addSongsToList" t:type="actionlink" ></a>
  		</t:loop>
     </body>
</html>

renders:
<html><head><link href="assets/tapestry/default.css" rel="stylesheet"  
type="text/css"><title>test</title></head><body><a  
href="test.addsongstolist" id="addSongsToList"></a><a  
href="test.addsongstolist" id="addSongsToList_0"></a><a  
href="test.addsongstolist" id="addSongsToList_1"></a></body></html>

Steve

On Apr 28, 2008, at 3:26:21, Chris Lewis wrote:

> Hi Steve,
>
> I'm not seeing that behavior in 5.0.12-SNAPSHOT, at least with
> pagelinks. When I don't provide a t:id, an id attribute is generated
> based on the component name and subsequent instances use a rolling
> scheme (pagelink, pagelink_1, etc). When I provide a component id
> (slightly different from the clientId) via t:id, that exact value is
> rendered in the resulting element. I imagine that would also use a
> rolling scheme if in a loop, but I haven't tried it.
>
> sincerely,
> chris
>
> Steven Woolley wrote:
>> Upgrading from 5.0.6 to the latest snapshot, I found that all my
>> pagelinks and actionlinks defined in tml like this:
>>
>> <a t:id="blah" t:type="actionlink" >link</a>
>>
>> re no longer rendering with the clientid, ie.:
>>
>> <a src="page.blah" id="blah">link</a>
>>
>> Instead, I get no id...
>>
>> Same thing goes for pagelinks...
>>
>> I can force the id to be rendered with:
>> <a t:id="blah" id="blah" t:type="actionlink" >link</a>
>>
>> but, that's kinda annoying, and if I render them in a loop, I no
>> longer get unique id's for each link....
>>
>> Am I missing something?  Is this a bug, or the way things will be in
>> the future?
>> Thanks,
>> Steve
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
> -- 
> http://thegodcode.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>


Re: actionlink and pagelink id's no longer (automatically) rendered in 5.0.12-snapshot

Posted by Chris Lewis <ch...@bellsouth.net>.
Hi Steve,

I'm not seeing that behavior in 5.0.12-SNAPSHOT, at least with
pagelinks. When I don't provide a t:id, an id attribute is generated
based on the component name and subsequent instances use a rolling
scheme (pagelink, pagelink_1, etc). When I provide a component id
(slightly different from the clientId) via t:id, that exact value is
rendered in the resulting element. I imagine that would also use a
rolling scheme if in a loop, but I haven't tried it.

sincerely,
chris

Steven Woolley wrote:
> Upgrading from 5.0.6 to the latest snapshot, I found that all my
> pagelinks and actionlinks defined in tml like this:
>
> <a t:id="blah" t:type="actionlink" >link</a>
>
> re no longer rendering with the clientid, ie.:
>
> <a src="page.blah" id="blah">link</a>
>
> Instead, I get no id...
>
> Same thing goes for pagelinks...
>
> I can force the id to be rendered with:
> <a t:id="blah" id="blah" t:type="actionlink" >link</a>
>
> but, that's kinda annoying, and if I render them in a loop, I no
> longer get unique id's for each link....
>
> Am I missing something?  Is this a bug, or the way things will be in
> the future?
> Thanks,
> Steve
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>

-- 
http://thegodcode.net


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org