Re: [Trinidad 2.0] Relocatable Resources - API proposal

2009-11-16 Thread Matthias Wessendorf
1610 is now inside of the code... (rev: 880763) 1611 is having a new patch; following the MyFAces 2.0 source code. We did some testing and noticed that throughput is just slightly lower then w/o setParent() modification (+new lifecycle methods (see 1612)) On Tue, Oct 27, 2009 at 7:02 PM, Matthias

Re: [Trinidad 2.0] Relocatable Resources - API proposal

2009-10-27 Thread Matthias Wessendorf
I created two tickets: Renderer modification = https://issues.apache.org/jira/browse/TRINIDAD-1610 Event part (setParent() behavior) = https://issues.apache.org/jira/browse/TRINIDAD-1611 -Matthias On Mon, Oct 26, 2009 at 3:51 PM, Matthias Wessendorf mat...@apache.org wrote: oh, yeah... of

[Trinidad 2.0] Relocatable Resources - API proposal

2009-10-26 Thread Matthias Wessendorf
Hi, in order to avoid dependency to h:head/body/form BUT be able to support the Relocatable Resources feature, we should change our renderers for head, body and form to check for any component resource(s) that has been targeted to one of these guys. This would mean that something like this just

Re: [Trinidad 2.0] Relocatable Resources - API proposal

2009-10-26 Thread Matthias Wessendorf
oh, yeah... of course this can only work when we change our UIXComponentBase's setParent() to trigger the new PostAddToViewEvent event. A simple implementation of the setParent() is available here: