[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xindice-dev
Subject:    RE: Why XUpdateQueryResolver is declared final?
From:       "STONE,ROBERT (HP-SanDiego,ex1)" <bob.stone () hp ! com>
Date:       2003-06-17 16:34:58
[Download RAW message or body]

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:Kevin.Ross@iverticalleap.com]
Sent: Monday, June 16, 2003 7:40 PM
To: xindice-dev@xml.apache.org
Subject: RE: Why XUpdateQueryResolver is declared final?


Final modifier removed in CVS version.

-Kevin Ross

-----Original Message-----
From: STONE,ROBERT (HP-SanDiego,ex1) [mailto:bob.stone@hp.com] 
Sent: Friday, June 13, 2003 6:42 PM
To: 'xindice-dev@xml.apache.org'
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
[prev in list] [next in list] [prev in thread] [next in thread]