I have completed the conversion already including the Acegi and
removal of all JSP and including templates from Facelets. There are
a number of other conversions including replacing the entire menuing
system with a facelets based menuing system from Richfaces. You can
find the updated code in the project swoop on sourceforge. If you
have any questions feel free to send me an email or give me a call.
Since I get over 1000 emails a day you might want to give me a heads
up if you send anything. I also have much of the a4j toolset
implemented as well.
Scott Ryan
CTO Soaring Eagle L.L.C.
Denver, Co. 80129
www.soaringeagleco.com
www.theryansplace.com
(303) 263-3044
[EMAIL PROTECTED]
On Oct 14, 2007, at 8:54 AM, Paul Katsev wrote:
Hi,
I'll try to clarify my statement. AppFuse JSF Basic comes packed
with everything under the Sun (pun intended): jsp + JSF(either
myfaces or reference) + facelets + much much more.
Many of the common pages in the initial project such as login.jsp
and bunch of admin pages are implemented using JSF+jsp, which is
done really well (Matt really knows his stuff). The trouble is
that AppFuse uses sitemesh for decoration and templating which is a
jsp native technology and doesn't play well with facelets (xhtml)
files. Same goes in reverse: facelets can't decorate jsp's. So if
you need advanced templating and decoration and want to use only
one technology (facelets or sitemesh) you will probably want to
choose facelets and throw sitemesh out. But when you do that, you
face the need to rewrite all those jsp pages that come with AppFuse
into jsf+facelets so that you can decorate them with facelets.
Decorating with facelets would also imply rewriting a bunch of
decoration related files: default.jsp, header.jsp, footer.jsp,
meta.jsp, messages.jsp, so on. Some are more trivial than the
others but it's doable. I like struts-menu which Matt uses. But
that's one thing that will most likely need to be sacrificed for
facelets decoration, but there are alternatives.
I'm almost done with converting all appfuse jsp's into faceltets.
I've finished all of the decorative files, except the menu (still
choosing a solution).
Login.jsp is difficult and I will need to spend some time learning
acegi before I can tackle that one. I will contact Matt as soon as
I'm done to find out if this is something AppFuse project and it's
community could benefit from and maybe make those files available
to everyone.
As to your problem: no there shouldn't be any problem using facelets
+jsf, in fact you don't even need to change the default *.xhml
suffix to anything else. Everything is there and should be able to
navigate to your page by calling http:// ... /mypage.html.
Tschuss
On 10/14/07, nasim salehi <[EMAIL PROTECTED]> wrote:
Hello,
I was searching about a problem which I've encountered during
development via AppFuse(JSF) which accidentally met your email,I
just want to know about this sentence you've left there:
In fact, I'm not sure why AppFuse(JSF) doesn't come with exclusively
facelets+jsf pages
I want to know if there is any problem using facelet+jsf together
in an application based on appfuse?
Did you really meant this from your sentence?
I'm using jsf pages in appfuse and I can't see my that pages,when I
invoke my jsf page in browser
I received this message:"The page your requested was not
found",I've added faces servlet entry in web.xml and use *.faces
pattern for my pages but when invoke the jsf page I can't see the
page.Do you have any idea about this?
It would be great if you have any info related to this.
--
my best wishes,
