On 03/07/2013 12:41 PM, Arne Vajh?j wrote:
On 3/7/2013 5:39 AM, Arved Sandstrom wrote:
My next big Java-space web app development effort is going to be
shifting away from JSF. I've been using the framework for 8 or 9 years,
and I'm unhappy with it.
[ SNIP ]
Sounds as if you may like RoR.
:-)
Maybe, maybe not. When I said that my web work was basically mostly or
all CRUD, I was overly simplifying. While ultimately it *is* mostly
CRUD, there are always business rules and workflow associated with what
CRUD is going to happen, so the pages may be complex and not just
straightforward list+add+delete+edit RoR-type pages. Mind you, I only
looked at RoR once and casually about 3 or 4 years ago.
It might be more accurate for me to say that the web page actions are
always CRUD-like, they are affecting state of something. That might be
session state, view state, JPA extended state, or database state (upon a
commit). Doesn't really matter what state it is.
But the generated HTML might be - often is - quite complex. Not
predictable by any scaffolding type system.
What I'm getting at is, it seems to me like everyone out there who built
a web framework got fixated on the idea that you have to have page
templates *and* code behind. Different artifacts altogether, and you
always need two or more to implement a delivered page. And considering
how tightly bound these pairs of template + codebehind usually are, why
do we have two artifacts anyway? Separation of concerns? No, the things
are inextricably bound together. Ease of development or maintenance? Not
bloody likely - you're forever jumping between at least two source files
to get things done.
So why not just have a single code artifact that implements a page?
That's one of my arguments.