ExtendedRenderKitService.encodeEnd() and
encodeFinally(). That second half is the bigger trick,
especially because you really have to do
ExtendedRenderKitService.encodeBegin(), etc. exactly
once per page, not multiple times.
-- Adam
On 2/22/07, Stefan Podkowinski [EMAIL PROTECTED] wrote:
Adam,
I think
of tackling this one?
I didn't have any great ideas.
-- Adam
On 2/21/07, Stefan Podkowinski [EMAIL PROTECTED] wrote:
Created the issue in jira.
https://issues.apache.org/jira/browse/ADFFACES-387
I'll hopefully be able to contribute a patch in the coming week, if I
have the time
for the misunderstanding. So this is a tougher nut
to crack. I can imagine some hacks to try to
instantiate the rendering context on the fly, but
nothing really obvious and bulletproof comes to mind.
I think we need a JIRA issue...
-- Adam
On 2/20/07, Stefan Podkowinski [EMAIL PROTECTED] wrote:
Hi Adam
I
. You're using Facelets. You need to configure things
a bit differently than without Facelets. Check out:
http://wiki.apache.org/myfaces/Facelets_with_Trinidad
-- Adam
On 2/16/07, Stefan Podkowinski [EMAIL PROTECTED] wrote:
I just tried the other way around by setting trinidad as default
render
, we rebranch every once in awhile, and the URL changes
when we do.)
-- Adam
On 2/15/07, Stefan Podkowinski [EMAIL PROTECTED] wrote:
Hello
Currently it does not seem to be possible to use trinidad with jsf1.2
ri and facelets and not having trinidad declared as default rendering
kit
an automated build going for
this branch.
(FYI, we rebranch every once in awhile, and the URL changes
when we do.)
-- Adam
On 2/15/07, Stefan Podkowinski [EMAIL PROTECTED] wrote:
Hello
Currently it does not seem to be possible to use trinidad with jsf1.2
ri and facelets and not having trinidad
Hello
Currently it does not seem to be possible to use trinidad with jsf1.2
ri and facelets and not having trinidad declared as default rendering
kit.
Removing
default-render-kit-idorg.apache.myfaces.trinidad.core/default-render-kit-id
from faces-config.xml and adding the render kit
