use Trinidad2 :-)
On Tue, Feb 23, 2010 at 7:25 AM, cristiJ cristi_ju...@yahoo.com wrote:
i checked out icefaces and primefaces. I think I'm going to wait untill
Tomahawk will be released for JSF 2.0.
Apache has done tremendous work so far.
I hope you willl have time to upgrade Tomahawk soon
we're on it!
2010/2/23, cristiJ cristi_ju...@yahoo.com:
i checked out icefaces and primefaces. I think I'm going to wait untill
Tomahawk will be released for JSF 2.0.
Apache has done tremendous work so far.
I hope you willl have time to upgrade Tomahawk soon
Jakob Korherr wrote:
Maybe
Discussion
Subject: Re: AW: Stuck making JSF 2.0 work with MyFaces
use Trinidad2 :-)
On Tue, Feb 23, 2010 at 7:25 AM, cristiJ cristi_ju...@yahoo.com wrote:
i checked out icefaces and primefaces. I think I'm going to wait untill
Tomahawk will be released for JSF 2.0.
Apache has done tremendous work so
Hi,
could you please post your config files?
In my opinion there is a configuration problem which avoids the container to
process your facelet...
Yours,
Martin
Von: cristiJ [mailto:cristi_ju...@yahoo.com]
Gesendet: Mo 22.02.2010 16:48
An:
Hi Martin,
Thnak you for replying, I'm starting to get a little desperate with this
problem. I'm pretty sure the config files are proper. This is part of my
web.xml :
context-param
param-namejavax.faces.FACELETS_LIBRARIES/param-name
Hi,
Am I getting this right: also your h: and your f: components are not
displayed correctly?
If so, either your configuration or the URL with which you access the site
are wrong. You need to include /faces/ or *.jsf (or something similar,
depending on your configuration) in your URL to get the
Hi,
Yes, you understood correctly, neither of h: or f: components are not
processed.
I have a very simple index.xhtml file :
?xml version='1.0' encoding='UTF-8' ?
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
html
Hi,
Does your URL in your browser include /faces/index.xhtml?
Regards,
Jakob
2010/2/22 cristiJ cristi_ju...@yahoo.com
Hi,
Yes, you understood correctly, neither of h: or f: components are not
processed.
I have a very simple index.xhtml file :
?xml version='1.0' encoding='UTF-8' ?
Hi,
yes, I just tried it. For both of theses URLs :
http://localhost:8080/app02/faces/index.xhtml
http://localhost:8080/app02
the file does not get translated to XHTML, it arrives in the browser with
the f and h customs.
This happens only when I add MyFaces.
I tried adding my self a custom
Maybe tomahawk is causing the problems, because there is currently no real
working branch of tomahawk for JSF 2.0. However there will be one soon.
Please remove tomahawk completely from your webapp and try again!
Regards,
Jakob
2010/2/22 cristiJ cristi_ju...@yahoo.com
Hi,
yes, I just tried
I just noticed on http://myfaces.apache.org/tomahawk/index.html that there is
support only for JSF 1.1 and JSF 1.2, I wished I would have noticed sooner.
Any ways, great work on MyFaces, and please add support for JSF 2.0 as soon
as possible.
Jakob Korherr wrote:
Maybe tomahawk is causing
Are you trying to use JSF 2.0 features or what? Currently, Myfaces and
Tomahawk 1.x versions c
On Mon, Feb 22, 2010 at 10:26 AM, cristiJ cristi_ju...@yahoo.com wrote:
I just noticed on http://myfaces.apache.org/tomahawk/index.html that there
is
support only for JSF 1.1 and JSF 1.2, I wished
Accidentally pressed the send button too soon.
What JSF 2.0 core library are you using? I don't think the problem you are
having with tomahawk not rendering is caused by Tomahawk not being based on
JSF 2.0.
-R
On Mon, Feb 22, 2010 at 10:55 AM, Richard Yee richard.k@gmail.comwrote:
Are you
: Re: AW: Stuck making JSF 2.0 work with MyFaces
An: MyFaces Discussion users@myfaces.apache.org
Datum: Montag, 22. Februar, 2010 20:03 Uhr
Accidentally pressed the send button
too soon.
What JSF 2.0 core library are you using? I don't think the
problem you are
having with tomahawk
i checked out icefaces and primefaces. I think I'm going to wait untill
Tomahawk will be released for JSF 2.0.
Apache has done tremendous work so far.
I hope you willl have time to upgrade Tomahawk soon
Jakob Korherr wrote:
Maybe tomahawk is causing the problems, because there is currently
15 matches
Mail list logo
