The reason is one of philosophy. And there has been some debate over
this on the dev lists. I think Andrew has something which may be thrown
into the sandbox.. however..
Trindiad renderkit works off the assumption that most of your content
will be trinidad content. As such, it has PPR built in to each
component and the famework necessary to support that PPR. Components
external to Trinidad are assumed to be able to do their own PPR and that
is where the philosophy comes in. Trinidad does not try to PPR the
world, it only tries to ppr itself so it can better optimize.
Some renderkits (like A4J) take the opposite approach and basically look
at adding AJAX functionality to existing non-ppr enabled
renterkits/content. Maybe you would be better off using a technology
like that instead of Trinidad for your application.
Scott
Stephen Friedrich wrote:
I have some very specific components in my project, made using facelets
and containing mostly pure html (with some ui:repeat thrown in).
How am I supposed to make such a component the target of PPR?
Why isn't there a simple non-rendering trinidad component for that
purpose, e.g.
<tr:fragment partialTriggers="region">
... html ...
</tr:fragment>
That component could also have a rendered attribute which is nicer than
using <c:if> (and avoids confusing facelets).
Is there any other component that I could misuse for that?
