IMOHO, Your Actions should be the only thing accessing the peer classes. All your JSP should be doing is receiving lists and/or OM objects themselves. The JSP should only be your View component, and should not have any hand in changing the state of you permanent storage mechanism i.e. you database. The extent of the JSP's job should only be to format the display of information received from the Controller (your action) and control page flow.
It is even better to hide your peer access from your actions using a service that has more general access methods than doSelect, doUpdate, etc. Disclaimer: I don't use JSP with Turbine, so my thoughts may be totally off base relative to the whole JSP thing. But I would think that the Turbine paradigm of MVC+1 would apply regardless of your templating language. my $0.02, Scott > -----Original Message----- > From: Jesse Chen [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, March 26, 2002 2:37 PM > To: Turbine Users List > Subject: bridging om peers and jsp/beans > > > Turbine newbie question: > > I'm currently using Turbine w/ jsp's and trying to understand > how to get > data from om peer objects on to the jsp page (the the proper > way intended by > the framework). Is it preferable to write JavaBeans that > call/manage the > peer classes and then use jsp tags to display the values? Any > insights, > general or specific (sample syntax) would be greatly appreciated. > > thanks, > > J > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> >
