Bob,
Yes "triggers" as the result of XUpdates would be very nice and is probably a common need.
Could we get your patch (or subclass stubs)?
Stephen Gaito
([EMAIL PROTECTED])
-------------------------------------------------------------------
From the [EMAIL PROTECTED] archive:
-------------------------------------------------------------------
From: STONE,ROBERT (HP-SanDiego,ex1) [mailto:[EMAIL PROTECTED]]
Sent: 2003-06-17 16:34:58
To: '[EMAIL PROTECTED]'
Subject: RE: Why XUpdateQueryResolver is declared final?
Thanks!
By the way, JMS code works great, I enabled it both for the updates and
XUpdate. I know that some of the commercial packages like Ipedo provide this
functionality, is it something that may interest Xindice users also?
Bob Stone
-----Original Message-----
From: Kevin Ross [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 16, 2003 7:40 PM
To: [EMAIL PROTECTED]
Subject: RE: Why XUpdateQueryResolver is declared final?
Final modifier removed in CVS version.
-Kevin Ross
-----Original Message-----
From: STONE,ROBERT (HP-SanDiego,ex1) [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 13, 2003 6:42 PM
To: '[EMAIL PROTECTED]'
Subject: Why XUpdateQueryResolver is declared final?
Hi all,
I work on project where the XUpdate query triggers JMS message. One
possibility would be to extend XUpdateQueryResolver class but it's
declared
final. Is there some security or other considerations for doing that?
Thanks,
Bob Stone
