WirehoseChangeNotification

David Griffith <[email protected]>
Newsgroups gmane.comp.web.webobjects.devel
Message-ID <[email protected]>
Hi all,

I've just started using WirehoseChangeNotification and I am  
experiencing a strange behaviour.  Basically there are three apps  
that need to notify each other.  One App 1 is mostly for display and  
is updated using App 2.  App 2 has been told to send notifications to  
App 1 and it appears to work.

However, when I change a value on the Product table and save it in  
App 2, it sends a notification to App 1 but the product suddenly  
disappears from the category that it belongs to on App 1.  You can  
search for the product and find it.  But it does not appear in the  
category it was in before.  Eventually it appears back again.

I've done some testing on it and basically what I have found is this:

There is some code to filter the products that are displayed.  In  
this code, I refer to category.products() being the products that  
belong to that category (using a relationship as normal).

While stepping through products, for each one I assign the current  
product in the array to currentProd.  I test the value of  
currentProd.prodActive() directly after and it returns true.
Then I use an if statement based on the same value.  It basically says :

if (currentProd.prodActive() == Boolean.TRUE)
	do this
else
	do that

Even though currentProd.prodActive() is returning true, it is  
entering the 'else' clause.
Testing the value of currentProd.prodActive() in the else clause also  
return true.

So basically, the value is always true, but it does not reflect this  
when the if statement is evalutated.

I'm just wondering has anyone ever seen something like this?  I  
worked perfectly before using Wirehose.  As I said, the product  
eventually does reappear.  It seems to be a temporary problem after  
the notification is sent.

Help!?!?

Thanks all,
Dave.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.