[xmlblaster-devel] Trouble with multiple subscibtions/callbacks

[Wolfgang Kleinertz <wolfgang.kleinertz at doubleslash.de>]

Hi!

I'm writing a program that uses an own callback for each subscibtion.
The problem is, that incomming messages won't be delivered to the
specialized callback. Instead, the default callback (registered while
login) gets the message, although
no subscribtion is running for this callback. Why?

An examples of an addressed message key:
  <key oid='agent-192.168.10.218___FRT1___log' contentMime='text/xml/'
contentMimeExtended='log'>
      <location source='agent-192.168.10.218' driver='FRT1'  />
  </key>

The XPath-query I use to subscribe:
 
//key[ at contentMimeExtended='log']/location[ at source='agent-192.168.10.218'
and
 at driver='FRT1']


The analysis of the problem showed the following:
The returned subscibtionId is:
      
Subscription-192.168.10.211-null-1014388370206-208054022-1-192.168.10.211-7609-1014388469248-13

An incomming message needs the same id to be dispatched to the right
callback, but they are not the same. (An id of an incomming msg. was
'agent-192.168.10.218___FRT1___log' == oid!!!!)

Thus, if the oid of the key is set to a value, the msg can't be
dispatched via
org.xmlBlaster.client.protocol.xmlBlasterConnection.update(...) to the
right callback. If I don't use a msg-oid, it works well. But that's no
solution, because I need the oid to avoid more than one message per
type.

I think, it's not a feature, it's a bug. Isn't it?! :)

Any solution?


Cheers,
Wolfgang

begin:vcard 
n:Kleinertz;Wolfgang
x-mozilla-html:FALSE
url:www.doubleSlash.de
org:doubleSlash Net-Business GmbH
adr:;;Müllerstraße 12/1	;Friedrichshafen;Baden-Württemberg;88045;Deutschland
version:2.1
email;internet:Wolfgang.Kleinertz at doubleSlash.de
x-mozilla-cpt:;-3360
fn:Wolfgang Kleinertz
end:vcard