Hi all, Is there a way to instruct the Orion container to reload a bean instance without waiting for it to passivate and reactivate ?? Or has anybody found a configuration setting whereby the passivatoin timeout can be lowered for the Orion container ?? We have a situation where the database schema is being modifed by site "authors" using legacy non-EJB means... (ASP -> SQL Server...sigh). If an entity EJB is being used constantly it does not passivate, and hence does not re-activate and consult the database. So changing data in the database is not being reflected in the middle-tier. A dodgy approach to fixing this would be to add a checking routine in each EJB that would clear its state and make a call to its own ejbLoad at certain intervals...but I get the feeling that apart from being fairly slap-dash it may not wash well with any black magic that the container is doing behind the scenes with the EJBs anyway. Many thanks for any tips, Dave Elliot [EMAIL PROTECTED]
