When you say different beans, will they have different accessor methods? Even if the bean has a collection, you ultimately have to call accessor methods to build the table, save introspection.
On 7/6/06, Dan Langer <[EMAIL PROTECTED]> wrote:
Antonio, Thanks for the suggestion. From a design POV, it seems odd that a piece of functionality (the beanName attribute) would be there when invoked one way (JSP), but not when invoked another (XML definition). Regardless of that, I'm curious about the suggestion you've made. My goal was to create a generic tile (to display a table), and then to pass it different beans depending on what data I wanted to show. I've created a definition for the generic one, but I can't think of how to use JSTL (useBean is what I assume you're suggesting) to allow me to pass the bean name as an "argument" to the tile when, it's defined using inheritance in the XML definitions file (my plan was to extend the generic one for each of the various types of data I was going to display). Thanks for your help, Dan -----Original Message----- From: Antonio Petrelli > How do you do this when you're using tile definitions (centralized into > one file)? This > > <put name="headerInfo" beanName="gridC"/> > > isn't valid within a <definition> according to the DTD. > I think you cannot do it (for now). Anyway you can use JSTL and Struts tags to manage bean inside your JSPs as you do in JSPs without Tiles. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
