Does JSF complement JSP, or is it independent?
Hello Everyone,
I have never tried JSFs, but I've read and heard from others that it is an MVC framework like Struts/ Spring MVC. I have very limited knowledge of MVC.
I've only recently begun updating my knowledge of JSP2.0 and I have a reasonable understanding of JSTL1.1
On some old articles written back in 2004 I read that JSF doesn't properly integrate with JSPs. I don't know if this is still the case.
Now, my worry is that does JSF replace JSP? or does it work with JSPs?
Should I dump JSPs and begin learning JSF?
Please guide me in the right direction, your input is appreciated.
[639 byte] By [
appy77a] at [2007-11-26 15:17:20]
# 1
I see that my question is answered here:
http://java.sun.com/products/jsp/
So JSF 1.2 does complement JSP 2.1 and there are changes to expression language that makes it Unified EL, and JSTL is also integrated with JSF allowing one to seamlessly use tags like c:for
Based on that info, I'll continue learning JSP2.1 and then move on to JSF with probably Apache MyFaces.
Message was edited by:
appy77
# 2
What I've found is that JSF does a pretty good job of replacing JSP tags and scripts. In fact, I'd say that if someone had JSP snippets in their JSF code, they're probably not using JSF to its full potential.
In my first JSF project, I included quite a bit of JSP. Then, as I learned JSF better, I realized that I could've used straight JSF for everything.
Since then, I think I've only ever had one instance where I had to use JSP because JSF just couldn't do it.
With that said, JSF certainly does build off of J2EE (including JSP). And it helps to have an understanding of JSP.
CowKing
# 4
I use JSF out of the box. If I need a component, then I create one. Maybe I am reinviting the wheel with some components, but I like to have it all in my own hands =)
Anyway, the JBoss Seam looks very interesting. JSF and EJB integrated in one packet. I think I will try out this one shortly to check if it has really advantages over my EJB and DAO designs.
# 6
Just to share...
I started using JSF out of the box but core jsf has some know issues with a few components like datatable and commandlink,
which are resolved in myfaces. so i would suggest of using myfaces instead of starting with core jsf, then getting stuck & then move to myfaces.
Moreover, you can use all jsf tags with myfaces as is. The advantage you get is myfaces implementation of these tags is more reliable as compared to core jsf.
