We don't generate our message from the database but from another
application that is actually in VB (This parts is not done yet, but
that's how we intend to do it). But I think, there could be a way to do
it from the database, but we won't be investigating this solution.
By the way thanks to all the team for your devotion and quick answer :)
Francois Archambault
> -----Message d'origine-----
> De: marc fleury [SMTP:[EMAIL PROTECTED]]
> Date: 18 avril, 2001 16:55
> À: [EMAIL PROTECTED]
> Cc: Jboss-Development@Lists. Sourceforge. Net
> Objet: RE: [JBoss-user] Flushing Cache (For Simone ?)
>
> That is pretty cool post it to jboss-dev francois,
>
> |So we created our own LRUEnterpriseContextCachePolicy class to be
> able
> |to passivate beans with JMS messages. We actually call the ageOut
> |method with the beans key we want to flush by going through the
> LRUList
> |obtains from getList() method. But there is still a problem, the
> beans
> |that are in a transaction don't get passivated.
>
> I believe it is a brilliant idea with the wrong implementation, it
> belongs
> at the Option A/B/C that informs the container that he should be
> updating
> the state of the beans. In other words, passivating is the wrong
> thing to
> do you want to be working in the synchronization interceptor.
>
> However I can't remember how you would want to navigate to the
> interceptor
> and probably the best way is to set that information on the wrapper,
> then
> have the synchronization interceptor call the load method depending on
> this
> flag.
>
> I am doing a class at www.jboss.org and I might try to get the
> students to
> implement this container feature on Friday, that is a really cool
> feature.
> Do you have the "JMS" stuff, how do you generate it from the database?
>
> marc
>
****** original message *********
> Hi,
>
> We have the following problem :
>
> 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".
>
> But we do want to keep the cache, because it is more efficient.
>
> So we created our own LRUEnterpriseContextCachePolicy class to be able
> to passivate beans with JMS messages. We actually call the ageOut
> method with the beans key we want to flush by going through
> the LRUList
> obtains from getList() method. But there is still a problem, the beans
> that are in a transaction don't get passivated.
>
> How can we ensure that all the beans we want to be passivate get
> passivated and that, wathever is the age of the bean ?
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
