You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Denis Stepanov (Created) (JIRA)" <ji...@apache.org> on 2012/01/27 10:56:41 UTC
[jira] [Created] (TAP5-1834) Warn user or disallow zone with
randomly generated id
Warn user or disallow zone with randomly generated id
-----------------------------------------------------
Key: TAP5-1834
URL: https://issues.apache.org/jira/browse/TAP5-1834
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.2.5, 5.3
Reporter: Denis Stepanov
Zone with an id generated randomly(ajax request) is useless and confusing developers, is such case there should be a warning or even an exception.
TAP5-1746
http://www.mail-archive.com/users@tapestry.apache.org/msg57958.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Created] (TAP5-1834) Warn user or disallow zone with
randomly generated id
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
On Fri, 27 Jan 2012 11:32:36 -0200, Denis Stepanov
<de...@gmail.com> wrote:
>>> Zone with an id generated randomly(ajax request) is useless
>>
>> It isn't (I've explained it in this thread:
>> http://www.mail-archive.com/users@tapestry.apache.org/msg57958.html),
>> otherwise Tapestry committers wouldn't care to implement.
>
> You have only explained why there are random ids, I'm not saying there
> are bad just in this case a zone with a random id is useless.There is
> only one way how to use random id zone is to extract its id after
> rendering and honestly I don't think is the right way.
Just provide a client id and Tapestry won't change it.
> Most developers will not understand why a zone inside a zone doesn't
> work without knowing all nuances, some kind of warning or even error
> which will tell to provide explicit id whould be nice.
I agree that the documentation should warn about components without
developer-provided ids inside zones.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] [Created] (TAP5-1834) Warn user or disallow zone with randomly generated id
Posted by Denis Stepanov <de...@gmail.com>.
>> Zone with an id generated randomly(ajax request) is useless
>
> It isn't (I've explained it in this thread: http://www.mail-archive.com/users@tapestry.apache.org/msg57958.html), otherwise Tapestry committers wouldn't care to implement.
You have only explained why there are random ids, I'm not saying there are bad just in this case a zone with a random id is useless. There is only one way how to use random id zone is to extract its id after rendering and honestly I don't think is the right way.
Most developers will not understand why a zone inside a zone doesn't work without knowing all nuances, some kind of warning or even error which will tell to provide explicit id whould be nice.
On 27.1.2012, at 13:32, Thiago H. de Paula Figueiredo wrote:
> On Fri, 27 Jan 2012 03:22:58 -0200, Paul Stanton <pa...@mapshed.com.au> wrote:
>
>> Just a side note, this has caught a few users over time (since t5.1).
>>
>> Boris' expected behaviour does not seem to me to be too unrealistic an expectation! Depending on your personality type ;) you may even consider this a bug.
>>
>> Maybe the zone re-rendering process should handle this client id changeover gracefully?
>
> The non-developer-provided ids change because otherwise the page could have different elements with the same id after a zone update. Automating the EventLinks (and ActionLinks) to point at new ids is quite hard: Tapestry would need to keep a server-side map of which link points to each zone, figure out which ids changed and then send a (EventLink, new target id) change them after a zone update. This would probably need to rewrite all JavaScript code related to zones. You can avoid this by providing client-side ids to Zones, so I don't think this whole change is worth.
>
> --
> Thiago H. de Paula Figueiredo
> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor
> Owner, Ars Machina Tecnologia da Informação Ltda.
> http://www.arsmachina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
Re: [jira] [Created] (TAP5-1834) Warn user or disallow zone with
randomly generated id
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
On Fri, 27 Jan 2012 07:56:41 -0200, Denis Stepanov (Created) (JIRA)
<ji...@apache.org> wrote:
> Zone with an id generated randomly(ajax request) is useless
It isn't (I've explained it in this thread:
http://www.mail-archive.com/users@tapestry.apache.org/msg57958.html),
otherwise Tapestry committers wouldn't care to implement.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] [Commented] (TAP5-1834) Warn user or disallow zone with
randomly generated id
Posted by "Thiago H. de Paula Figueiredo (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194782#comment-13194782 ]
Thiago H. de Paula Figueiredo commented on TAP5-1834:
-----------------------------------------------------
On Fri, 27 Jan 2012 11:32:36 -0200, Denis Stepanov
Just provide a client id and Tapestry won't change it.
I agree that the documentation should warn about components without
developer-provided ids inside zones.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
> Warn user or disallow zone with randomly generated id
> -----------------------------------------------------
>
> Key: TAP5-1834
> URL: https://issues.apache.org/jira/browse/TAP5-1834
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3, 5.2.5
> Reporter: Denis Stepanov
>
> Zone with an id generated randomly(ajax request) is useless and confusing developers, is such case there should be a warning or even an exception.
> TAP5-1746
> http://www.mail-archive.com/users@tapestry.apache.org/msg57958.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1834) Warn user or disallow zone with
randomly generated id
Posted by "Denis Stepanov (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194703#comment-13194703 ]
Denis Stepanov commented on TAP5-1834:
--------------------------------------
You have only explained why there are random ids, I'm not saying there are bad just in this case a zone with a random id is useless. There is only one way how to use random id zone is to extract its id after rendering and honestly I don't think is the right way.
Most developers will not understand why a zone inside a zone doesn't work without knowing all nuances, some kind of warning or even error which will tell to provide explicit id whould be nice.
On 27.1.2012, at 13:32, Thiago H. de Paula Figueiredo wrote:
> Warn user or disallow zone with randomly generated id
> -----------------------------------------------------
>
> Key: TAP5-1834
> URL: https://issues.apache.org/jira/browse/TAP5-1834
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3, 5.2.5
> Reporter: Denis Stepanov
>
> Zone with an id generated randomly(ajax request) is useless and confusing developers, is such case there should be a warning or even an exception.
> TAP5-1746
> http://www.mail-archive.com/users@tapestry.apache.org/msg57958.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1834) Warn user or disallow zone with
randomly generated id
Posted by "Thiago H. de Paula Figueiredo (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194664#comment-13194664 ]
Thiago H. de Paula Figueiredo commented on TAP5-1834:
-----------------------------------------------------
On Fri, 27 Jan 2012 07:56:41 -0200, Denis Stepanov (Created) (JIRA)
It isn't (I've explained it in this thread:
http://www.mail-archive.com/users@tapestry.apache.org/msg57958.html),
otherwise Tapestry committers wouldn't care to implement.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
> Warn user or disallow zone with randomly generated id
> -----------------------------------------------------
>
> Key: TAP5-1834
> URL: https://issues.apache.org/jira/browse/TAP5-1834
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3, 5.2.5
> Reporter: Denis Stepanov
>
> Zone with an id generated randomly(ajax request) is useless and confusing developers, is such case there should be a warning or even an exception.
> TAP5-1746
> http://www.mail-archive.com/users@tapestry.apache.org/msg57958.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1834) Warn user or disallow zone with
randomly generated id
Posted by "Thiago H. de Paula Figueiredo (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194782#comment-13194782 ]
Thiago H. de Paula Figueiredo commented on TAP5-1834:
-----------------------------------------------------
On Fri, 27 Jan 2012 11:32:36 -0200, Denis Stepanov
Just provide a client id and Tapestry won't change it.
I agree that the documentation should warn about components without
developer-provided ids inside zones.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
> Warn user or disallow zone with randomly generated id
> -----------------------------------------------------
>
> Key: TAP5-1834
> URL: https://issues.apache.org/jira/browse/TAP5-1834
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3, 5.2.5
> Reporter: Denis Stepanov
>
> Zone with an id generated randomly(ajax request) is useless and confusing developers, is such case there should be a warning or even an exception.
> TAP5-1746
> http://www.mail-archive.com/users@tapestry.apache.org/msg57958.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1834) Warn user or disallow zone with
randomly generated id
Posted by "Thiago H. de Paula Figueiredo (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194664#comment-13194664 ]
Thiago H. de Paula Figueiredo commented on TAP5-1834:
-----------------------------------------------------
On Fri, 27 Jan 2012 07:56:41 -0200, Denis Stepanov (Created) (JIRA)
It isn't (I've explained it in this thread:
http://www.mail-archive.com/users@tapestry.apache.org/msg57958.html),
otherwise Tapestry committers wouldn't care to implement.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
> Warn user or disallow zone with randomly generated id
> -----------------------------------------------------
>
> Key: TAP5-1834
> URL: https://issues.apache.org/jira/browse/TAP5-1834
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3, 5.2.5
> Reporter: Denis Stepanov
>
> Zone with an id generated randomly(ajax request) is useless and confusing developers, is such case there should be a warning or even an exception.
> TAP5-1746
> http://www.mail-archive.com/users@tapestry.apache.org/msg57958.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1834) Warn user or disallow zone with
randomly generated id
Posted by "Denis Stepanov (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194703#comment-13194703 ]
Denis Stepanov commented on TAP5-1834:
--------------------------------------
You have only explained why there are random ids, I'm not saying there are bad just in this case a zone with a random id is useless. There is only one way how to use random id zone is to extract its id after rendering and honestly I don't think is the right way.
Most developers will not understand why a zone inside a zone doesn't work without knowing all nuances, some kind of warning or even error which will tell to provide explicit id whould be nice.
On 27.1.2012, at 13:32, Thiago H. de Paula Figueiredo wrote:
> Warn user or disallow zone with randomly generated id
> -----------------------------------------------------
>
> Key: TAP5-1834
> URL: https://issues.apache.org/jira/browse/TAP5-1834
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3, 5.2.5
> Reporter: Denis Stepanov
>
> Zone with an id generated randomly(ajax request) is useless and confusing developers, is such case there should be a warning or even an exception.
> TAP5-1746
> http://www.mail-archive.com/users@tapestry.apache.org/msg57958.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira