> > No, but what about
> >
> > <c:out value="${library.books[25].page[5].title}" /> ?
> > (not sure about the syntax).
> whats the problem?
> MVC usually allows 'read-only access to model' for the view
> Also the question is, what you expose to the view.
> If you are afraid that somebody will misuse the library entries -
don't
> expose them.
> I suppose MVC was the reason for JSP EL not to allow arbitrary method
> invocations. But I'd love to have such anyway ;)
>
> >...
> > And what about database access tags?
> You mean the jstl tags? They are there for quick and dirty.
> If you don't change anything in the database though, it still okay to
MVC.
> If you don't want it, don't expose your database in the first place ;)
>
>
The problem is, that if you give a user the possibility to misuse your
framework - he will.
And EL gives jsps more power than a dumb view should have. And if your
view isn't just layouting out the data, but performing nearly complex
operations, it's not dumb anymore, and a smart view doesn't fit into the
MVC.
If the user is allowed to break the paradigm he will.
If you have an architecture, which is built on a paradigm (and any good
architecture is) you can't allow the developers to break the paradigm,
or
the architecture will stop working one day, without obvious reasons.
It's probably why there are no pointers in java, even pointers adds cool
features to the language.
Regards
Leon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
