> > i think the loss of using interfaces is a big disadvantage. on the > > serverside it will not be clear, why i have a class User with getter > > and setter and a User2 with just setter. > > I disagree. I believe it's a huge advantage. It means that I don't have to > code server-side objects specifically for use with JSTL, and I > don't have to > retrofit existing objects just to make them available to my JSTL page > authors.
mmh?! in case i want the webdeveloper access only getters of my object, i need to write a wrapper object on the server side, as shawn bayern mention! so i have to write specific object for use with jstl:-(( leif -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
