Doh, missed a <bean:define toScope> ... regards
On 11/8/06, Greg Reddin <[EMAIL PROTECTED]> wrote:
On Nov 8, 2006, at 8:12 AM, Antonio Petrelli wrote: > Vinicius Carvalho ha scritto: >> I have a list that is going to be iterated, and the bean inside it >> will be checked, depending on a certain flag a tiles definition will >> be used to display the content, kinda like this: >> >> <logic:iterate name="someList" id="someBean'> >> <logic:equal value="SIMPLE" name="someBean" property="displayType"> >> <tiles:insert definition="def.simple"/> >> </logic:equal> >> <logic:equal value="COMPLEX" name="someBean" property="displayType"> >> <tiles:insert definition="def.complex"/> >> </logic:equal> >> And the list goes on ... >> </logic:iterate> >> >> Now, inside my tiles I need to access someBean. But I'm not being >> able >> to do so, I get an exception: Cannot find bean: "someBean" in any >> scope > > That's strange, in which scope did you put "someBean"? And how do > you access "someBean" in your tiles? Since the scope is not defined (can you define scope in the iterate tag? (It's ben a while)), I think someBean is in page scope. So, it's no longer in scope inside your tiles definition. You'll need it to be in request scope if you want everything to work the way you have it here. Greg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- IBM Certified SOA Solution Designer IBM Database Associate - DB2 UDB V8.1 Family Sun Certified Enterprise Architect (Part I) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
