I have checked it and did not find any problem. The script is invoked even during the ajax rre-rendering. May be you have there a wrong path to a file. Add some text to the timer.xhtml to see that it is included itself for sure.
Thanks for your time.
We solved it ;)..
Why is this btw?.. and is this realy necessary?
Well, the a4j:include instead of ui:include might be used to navigate between the sub-views (for partial navigation feature) where the same id are possible. To avoid such conflict, a4j:include combines together f:view and jsp:include.
More formal reason is a #9.2.2 of the JSF Specification:
- When using the <jsp:include> standard action (or the JSTL <c:import> action) to compose a single view from multiple JSP pages, all JSF component custom actions in included pages must be nested inside the <f:subview> custom action from the JSF Core Tag Library (which is itself nested inside the <f:view> custom action). The <f:subview> action itself may be present in the including page (i.e. with the <jsp:include> or <c:import> action nested inside it), or in the included page.