A good( or better ) site to post this kind of general question is at:

http://forums.itworld.com/webx?14@@.ee6bdcf/85!skip=21

> Hi all,
> 
> I've just finished the book and I hope I've simply missed the point but I
> can't see what the big deal is in using beans and tag libraries.
> 
> Since you can use any Java in a JSP why not just use the class you're
> creating to be a bean but without actually using it as a bean. Surely the
> introspection aspects of beans will slow things down and the interface to
> a bean isn't as rich as might be required but could be at least be coded
> if needed. Also the syntax in a JSP to use a bean is just as bad to the
> page designer as calling the 'raw' Java.
> 
> As to tag libraries couldn't these just be high level pieces of Java that
> generate, or not, output from the servlet. The only advantage I can see is
> the hidden 'linkage' between the various instances of a tag command in a
> single JSP.
> 
> I've got to persuade several teams that the use of JSP and tag libraries
> is the way forward as we've fallen into the trap of having servlets
> generate all the HTML or having the HTML full of code, which is currently
> PHP.
> 
> I have taken the time to read the book carefully and have looked at other
> examples but I think I must have missed the point somewhere along the line
> otherwise there wouldn't be the current trend to use such techniques.
> 
> Can anyone shine a light on what I'm missing.
> 
> Cheers,
> 
> Andy.