Hi Andy The issue It's not the "caching" mechanism, it's the ognl to bytecode compiler. Don't worry it's easy to fix. Create a common "interface" with the "getSomeProperty" method and make all your pages implement that interface. That should be all.
-- Alejandro Scandroli Amneris: We build process-driven web applications. http://www.amneris.es On Dec 20, 2007 11:47 AM, Andy Pahne <[EMAIL PROTECTED]> wrote: > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
