Re: [Shale] managed-bean-name token

2005-10-15 Thread Ryan Wynn
[EMAIL PROTECTED] (Gary VanMatre) wrote on 10/14/2005 10:20:58 PM: > I did some more looking and you are right. The managedBeanName of a > nested Clay component is being ignored. > I'll put in a fix for this one. Good catch and thanks for your persistence. > Gary Gary, thanks for the help. I

Re: [Shale] managed-bean-name token

2005-10-14 Thread Gary VanMatre
Ryan Wynn wrote: > Gary, I tried this approach in both forms you described and it seems that > the nested > Clay component is picking up the managedBeanName from the root Clay > component instead > of the one I specify. Which turns out to be the ViewController associated > with the view id.

Re: [Shale] managed-bean-name token

2005-10-14 Thread Ryan Wynn
[EMAIL PROTECTED] (Gary VanMatre) wrote on 10/14/2005 03:20:37 PM: > The managedBeanName attribute can only be set at the Clay component. > The subtree under the Clay component applies token replacement of > the literal string "managed-bean-name" with the value from the root. > > For full html

Re: [Shale] managed-bean-name token

2005-10-14 Thread Gary VanMatre
Hi Ryan, >I'm having trouble getting Shale clay to substitute a non-ViewController >bean for the token managed-bean-name. I have looked at the use cases and >I still feel like I don't understand the syntax to do token replacement. >Shale continues to reference my ViewController bean in EL expr