On 2004-11-11 at 11:24:14 +0100, Rosenberg, Leon wrote: > > > > -----Ursprüngliche Nachricht----- > > Von: Mark Lowe [mailto:[EMAIL PROTECTED] > > Gesendet: Donnerstag, 11. November 2004 11:04 > > An: Struts Users Mailing List > > Betreff: Re: talking about paradigms > > > > I don't think EL breaks the MVC pattern. Although it leaves you free > > to do so if you so wish. I don't see a world appart from using > > > > <bean:write name="person" property="name" /> > > > > <jsp:getProperty name="person" property="name" /> > > > > <c:out value="${person.name}" /> > > > > ${person.name} > > > 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 ;) >.. > Leon >.. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
