Thank you very much, Andrew Robinson.
You understanding is correct. This explaination is a good start point for me.
On 2/23/06, Andrew Robinson <[EMAIL PROTECTED]> wrote:
> Not 100% sure what you mean by a web layer, but I presume that you are
> refering to a new web project. I researched Struts, "Plain" JSF,
> JSF+Tiles, JSF+Facelets and finally settled on JSF+Facelets+Seam for
> my project.
>
> My home project is in development and is working fine. The only
> problems I have are when I I am working off of CVS/SVN latest to get
> the newest functionality. MyFaces 1.1.1 + Facelets 1.0.10 seems to be
> quite stable and my company is using that combination as well.
>
> The biggest issue/hurdle for me to deal with in development on both
> JSF as well as struts is that URLs may not be able to be bookmarked by
> users, as page validation occurs by posting back to the current URL
> before navigating to the new page (which is often done by a servlet
> forward and not a browser redirect).
>
> The learning curve on JBoss Seam is pretty steep for
> installation/setup, but JSF and facelets are pretty easy to understand
> if you are willing to do a bit of reading first (any of the online
> tutorials work, including Sun's).
>
> I was really hating JSF before I tried facelets. I don't recommend it.
> Tiles just doesn't work from an architectural perspective. Trying to
> work with view, subview and verbatim tags is ugly to be nice.
>
> Since pages contain no code like ASP, Perl, PHP, JSP, the pages are
> much more maintainable. The business code is nicely tucked away in
> Java beans (POJOs). I prefer JSF+Facelets over ASP.NET as well.
> ASP.NET has some powerful controls, but the binding is lackluster.
> ASP.NET also requires you to have backing code on every page, which
> maked it difficult to seperate out page developers from Java/code
> developers.
>
> The one thing I haven't heard too much about on these lists is
> performance for very large sites (I haven't heard either way - good or
> bad).
>
> Hope I answered your question instead of just babbling...
>
> On 2/22/06, Anthony Hong <[EMAIL PROTECTED]> wrote:
> > Hi Andrew Robinson,
> >
> > In your words, JSF with Facelet is good to use if start a new project
> > in web layer, Isn't it?
> > Becuase I am going to have a new project and we want to use something
> > new in web Layer. I want to know more about JSF in real project
> > whether we can start use it or not.
> > Thanks.
> >
> > On 2/22/06, Andrew Robinson <[EMAIL PROTECTED]> wrote:
> > > If you want JSF 1.2 and JSTL support I strongly recommend facelets.
> > > You can have your own tag handler for JSTL tags that are not yet
> > > supported, and there are several already supported. They tag handlers
> > > are processed before the JSF components, but other than that item, it
> > > is possible to feed EL statements into JSTL tags. For example:
> > >
> > > <c:choose>
> > > <c:when test="#{mybean.myprop}"/>
> > > <c:otherwise/>
> > > </c:choose>
> > >
> > > -Andrew
> > >
> > > FYI - I can't image using JSF without facelets. IMO, JSF is useless
> > > without facelets. Sun should make it part of the spec (IMO of course).
> > >
> > > On 2/22/06, Werner Punz <[EMAIL PROTECTED]> wrote:
> > > > Anthony Hong schrieb:
> > > > > I knew that JSF have something like tableset to render table like
> > > > > view easily.
> > > > > But sometime I have to write html table by self to offer flexibility.
> > > > >
> > > > > I saw Facelet to use with JSF as a view, Is it useful?
> > > > >
> > > > ah one thing, I do not no if there are facelet descriptors for the
> > > > jsf:html lib in existence so combining both might become problematic.
> > > >
> > > >
> > >
> >
> >
> > --
> >
> > Anthony Hong
> >
>
--
Anthony Hong
