Re: [Trinidad] tr:table varStatus not working for EL passed to included components

[Renzo Tomaselli]

Andrew, I cannot reproduce it as a simplified case. I tried to include a simple table component in a page. The table in turn includes a row component. All of this works fine - row indexes are output as expected. My real case is much more complex. In short, I have a number of nested container components, hosting runtime-defined real components. The page is nothing more than an initial empty container. This approach mimics frames and alike by means of using ui:include. I actually used a bean-provided row index as a definitive workaround. Thanks -- Renzo Andrew Robinson wrote: Could you whip up a quick and small demo and maybe I can find some time next week to have a look? -Andrew On Fri, Mar 21, 2008 at 3:13 AM, Renzo Tomaselli <[EMAIL PROTECTED]> wrote: No way, using ui:decorate yields pretty much the same results. Conversely - retrieving current row index from the bean works fine. I'm afraid this issue is going to be appended to a list of facelets mysteries. -- Renzo Andrew Robinson wrote: On Thu, Mar 20, 2008 at 2:20 PM, Renzo Tomaselli <[EMAIL PROTECTED]> wrote: Andrew, I don't use any template. Never used one, actually I rely heavily on composition components (many placeholders, one page). Maybe a trivial workaround for this issue is to have a row getter returning the row index, since #{row} is evaluated properly within the inner component. ui:composition, ui:decorate, ui:include and facelets user tags are all pretty much the same TagHandler. They don't share code, but their code is all very similar. So when you say: "where cx:valueHolder is an included component having:" you are using a template. facelet template, include, user tag all boil down to a Facelet class instance. So try the code I gave you instead of using cx:valueHolder. -Andrew