One thing I'm finding a little ugly using Shale is referencing the view controller using EL expressions. Due to the way Shale maps view IDs to backing bean names, I end up with ugly EL expressions like #{pages$user$profile$general.whatever}.

Would it make sense to store the view controller under a well-known (configurable) key, so you could instead write #{backing.whatever}? Shale could use a standard name (e.g. 'backing') by default and provide a configuration option to change this to whatever the developer wants.

There could also be a mechanism for setting the 'alias' on a per-view basis; perhaps an interface the view controller bean can optionally implement which would return the backing bean alias and/or allow it to be set as a managed property.

Are there situations that would make this a Really Bad Idea? I'm wondering if it might cause issues for view composition with Clay, for example.

Assuming there aren't major drawbacks to the idea, I'll try and work up a patch in the next day or so covering some or all of the points above.

Cheers,

L.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to