]
*To:* xmlblaster@server.xmlBlaster.org
*Sent:* Sun, 04 Mar 2007 12:43:27 -0500
*Subject:* Re: [xmlblaster] Not getting callback on erase
Hi Jonathan,
the proper way (also for native plugins) to erase messages is for
example:
System.err.println("HelloWorldN
Can RequestBroker.update be used to publish messages from a native plugin?
David Robison
_
From: Marcel Ruff [mailto:[EMAIL PROTECTED]
To: xmlblaster@server.xmlBlaster.org
Sent: Sun, 04 Mar 2007 12:43:27 -0500
Subject: Re: [xmlblaster] Not getting callback on erase
Hi Jonathan,
the
Hi Jonathan,
the proper way (also for native plugins) to erase messages is for example:
System.err.println("HelloWorldNative: Connecting with protocol
'LOCAL' to xmlBlaster\n");
I_XmlBlasterAccess con = new XmlBlasterAccess(glob);
ConnectQos qos = new ConnectQos(this.g
Jonathan Clark wrote:
As a followup to my previous email, it appears that the erased topics
are still in the database in
the case where they are erased from the plugin, but they do appear to
be cleaned up from the
database in the external service case.
Are there know side affects of using a c
As a followup to my previous email, it appears that the erased topics are still
in the database in
the case where they are erased from the plugin, but they do appear to be
cleaned up from the
database in the external service case.
Are there know side affects of using a client side connection fro
I have some code that runs as a separate service that generates topics and when
the message is
cleared, it then erases the topic after a predefined delay using the code below.
EraseQos eq = new EraseQos(glob);
eq.setForceDestroy(true);
EraseKey theEK = new EraseKey(glob, oid);
EraseReturnQos[] er
