The library has tags, which are for so commonly used component/validation/any presentation logic, that it became a framework as a whole.
Does it make any sense? Please correct me.
Thanks.
Sergey Smirnov
Ranch Hand
Joined: May 29, 2003
Posts: 167
posted
0
I do not think this is a correct assumption somehow.
g madhava
Ranch Hand
Joined: Sep 14, 2001
Posts: 85
posted
0
JSF uses custom tag libraries, but is not just a custom tag library. JSF offers many features like
1] It has a powerful lifecycle mechanism.(6 phases)
2] One can build custom components straight out of the java code. No need to use the "custom tag library" components.
3] Custom renderers..
etc...
ankur rathi
Ranch Hand
Joined: Oct 11, 2004
Posts: 3829
posted
0
Originally posted by g madhava: JSF uses custom tag libraries, but is not just a custom tag library. JSF offers many features like
1] It has a powerful lifecycle mechanism.(6 phases)
I guess, JSF (tags) are nothing in itself untill we use them in JSP page. So they can't make any changes in life cycle of JSP page...
Right?
Ilja Preuss
author
Sheriff
Joined: Jul 11, 2001
Posts: 14112
posted
0
JSF doesn't need to work with JSPs. The component model works well with other template frameworks.
So, no, JSF is not at all "just a tag library".
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus