I'm afraid that's a use case that wasn't foremost in my mind when coding this stuff up for T5. Still, if you explicitly set component ids, it's highly unlikely that they'll change dramatically from one build to the next ... could you elaborate on the situation that drove you towards this kind of solution?
On 3/23/07, Doug Hauge <[EMAIL PROTECTED]> wrote:
Is there a way to customize the generation of a unique client id from a component id? We would like to generate the unique id in such a way that it would not change across most modifications to a page, mainly so Selenium tests can be written that will work across page redesign. The current method of appending a suffix to a component id does not seem to allow this, so we would like to be able to generate a unique id by prepending the component ids of ancestral components. We could potentially implement our own PageRenderSupport service, but the 'allocateClientId' method only takes a string parameter, so we don't have the context we would need (in particular, the ComponentResources of the component for which we are generating the id). Thanks, Doug
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
