Hi everyone!
This was a specific question regarding a possible solution for our
problem. (I work with the author of the question). Now, maybe it would
be simpler and better to expose our problem and see what you people
think we should do.
The problem is that we have to deal with direct access to the underlying
database. We absolutely cannot make all accesses go through the EJB
layer (for now that is). While this is the case, we have to find ways to
make JBoss refresh the data from the physical database when it is
changed.
So we thought it would be simple to add a SSB to offer cache management
services to our "old" application to call. ie. make changes through
VB/ADO/OleDB application and "inform" the JBoss server that those tables
need to be "flushed".
We can make the passivation delay very short, but I think that would be
overkill...
Suggestions ?
Thanks!
Daniel
> Hi,
>
> I need to flush the cache manually. I already know that
> there is a tag
> <overager-period> that does an auto passivate on bean that are older
> than the <max-bean-age>. But how can I do a passivate
> manually on every
> bean in the cache when I need it.
You can't.
Why would you BTW ?
It seems to me that you should not care about passivation, it should be
transparent to you, shouldn't be ?
Simon
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
