I have a compomen "ItemDetails" which is used in many pages. In the component's template there is an ognl expression like "ognl:page.someProperty".
Unfortunatly this expression is cached (I think). page always evaluates to the first page that I opened after deployment. On the other pages a nasty class cast exception is thrown.
Is there a way to fine tune (or deactivate) ognl expression caching? Andy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
