Hello!
Of course, Martin, I have extensionFilter configured (I always
configure it even I not use extensions). I have a working project with
extfilter configured and etc. It is working fine with facelets 1.0.10
(and 1.0.7) & MyFaces 1.1.1. When I change MyFaces to the latest nigthly
I see no javascript output (this was my first try to use 1.1.2). Of
course, if org.apache.myfaces.ALLOW_JAVASCRIPT is false - the
application begin to work. Strange thing - when
org.apache.myfaces.ALLOW_JAVASCRIPT is false I see <!-- MYFACES
JAVASCRIPT --> and nothing more, and when
org.apache.myfaces.ALLOW_JAVASCRIPT is true I even can't see <!--
MYFACES JAVASCRIPT --> !!!
P.S. Without Facelets all is ok. So (IMHO) the problem is between
MyFaces and Facelets.
Martin Marinschek wrote:
Hi Boris,
we've been digging a lot in this area in the last two weeks, so this
feedback is important.
A question - do you have the extensionsFilter configured, or do you
not use extended components?
regards,
Martin
On 2/12/06, Boris Kovalenko <[EMAIL PROTECTED]> wrote:
Hello!
May be I missed something, but with latest 1.1.2 and Facelets I see no
javascript code in generated files. So command links and other things
stop working. There is no problem with 1.1.1 code.
With respect,
Boris
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
With respect,
Boris
