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
Are there know side affects of using a client side
connection from within a plugin? This seems
to be the only option to erase topics successfully from
within the plugin.
I have some code that runs
as a separate service that generates topics and when the message
cleared, it then erases the
topic after a predefined delay using the code below.
EraseQos eq = new EraseQos(glob);
EraseKey theEK = new EraseKey(glob,
EraseReturnQos eraseArr = con.erase(theEK,
When the erase
happens, clients listening on the topic receive a callback with the
set to true and can
react to the erase. However, I want to convert the code to run as a plugin
that it will only be
active when xmlBlaster is running. The code runs, but I have run into a
process the erase from within a plugin using the following code,
clients listening on
the topic do not receive a callback indicating the
updateKey = new UpdateKey(engineGlob,
msgQosData = new MsgQosData(engineGlob,
updateKey, null, msgQosData);
thoughts on why the external erases seem to get propogated and the internal
erases do not?
cases the topic appears to get erased, however, the clients do not know about
the erase in
second case. Test have been run under 1.5.1.