I also happen to read the JSF specification lately, I guess by using
JSF framework , i think we are looking at a framework that
doesnt restrict to HTML, HTTP and some other constraints that we are
used to.
May be I can quote the introduction here for you to understand what is
JSF and its punch line.

"JSF's core architecture is designed to be independent of specific
protocols and
markup. However it is also aimed directly at solving many of the common
problems
encountered when writing applications for HTML clients that communicate
via
1-8 JavaServer Faces Specification · February 2004
HTTP to a Java application server that supports servlets and JavaServer
Pages (JSP)
based applications.
JSF tackles the following challenges associated with these
applications:

Managing UI component state across requests

Supporting encapsulation of the differences in markup across
different browsers
and clients

Supporting form processing (multi-page, more than one per page, and
so on)

Providing a strongly typed event model that allows the application to
write
server-side handlers (independent of HTTP) for client generated events

Validating request data and providing appropriate error reporting

Enabling type conversion when migrating markup values (Strings) to
and from
application data objects (which are often not Strings)

Handling error and exceptions, and reporting errors in human-readable
form
back to the application user

Handling page-to-page navigation in response to UI events and model
interactions."

Guess the gist is more than this.

Rgds
Sanjay

I am really glad you started this thread. I had similar questions a few
months ago in this group and I guess I didn't expose my idea clearly
enough: I got only two answers telling something like "framework sucks"
with no real explanation.
I am currently working on a new web application, which today is basic
ASP, i.e. presentation, business logic and UI control are all mixed in a
indigestable (does that word exist ? :) ) messy soup of M$ code.
We are moving to J2EE, and we are exploring the differenct frameworks.
We came to similar conclusions: frameworks are great stuff to help you
do basic or "not-too" advanced web-app. But as soon as you have specific
need, or you want something the meets only your needs (i.e. not a
generic reusable multipurpose code) to optimize the application, then
the only way we found is to design our own framework.
The task is not too complex, as we got our inspiration from those
existing framework, but we take only the things that are usefull to us
and rebuild it the way we need it.
It has however a drawback: if you have an important turn-over in your
staff (here in Thailand this is crazily important), then the new staff
has to learn your framework. The learning curve is a little bit slower.
If you use struts for ex., then in your job description you can filter
easily.
Also, the framework you design might need some time to be "bullet-proof"
and stable.
One good point is that it is interesting to design and create.

But we really think it is better this way and we are actually quite
confident in what we have done so far. We are not done yet, but I would
say we are about 40% from a nice (small) framework.

Good luck

There is nothing wrong with it.  After all, these frameworks are also
built on top of those technologies as well.  It sounds as if you already
have a framework of your own code built up.  So unless you find it too
complicated, too slow to develop in or too difficult to maintain just
keep on truckin'.

HTH,
Ray