I was waiting for your feedback here, Sylvain ;) I know this is problematic, for the reasons you pointed out. As things like addResource and the scroll-position javascript are special MyFaces functionality anyways, the user won't have the special features anyways with using the RI, so no change here.
With using MyFaces, he won't get the functionality if he doesn't use t:head or t:body. It will still work, he just won't have the extras. regards, Martin On 9/27/05, Sylvain Vieujot <[EMAIL PROTECTED]> wrote: > Hello Martin, > > I'm not sure I understand this. > Would you require every page having a t:component to have t:head & t:body > components as well ? > > If this is the case, it would be a lead to a lot ot other problems I think. > For example, it would break old pages. Also, you could not include just a > t:component in a page that would otherwise for fine with the RI. > > Sylvain. > > > On Tue, 2005-09-27 at 12:33 +0200, Martin Marinschek wrote: > Hi *, > > There is a long standing bug MYFACES-152 > > http://issues.apache.org/jira/browse/MYFACES-152 > > which needs our attention, for facelets and ADF faces compatibility. > > What do you say to my suggestion to move writing these scripts to the > encodeEnd Method of a newly created t:head/t:body component? > > With this approach, we could also support including component > resources in the header much better, as we have a clear marker for the > major areas of the HTML page... > > regards, > > Martin > > -- http://www.irian.at Your JSF powerhouse - JSF Trainings in English and German
