JMS-style Topics

[Jonathan Allen]

The .Net program I am writing needs to use JMS-style topics. Is there a way
to make a MS Message Queue work like a JMS Topic. Or is there a way to
access a JMS Topic (preferable WebLogic 8) from a .Net application.

Requirements:
Multiple listeners on one queue.
All listeners get all messages.
Messages are deleted after all active listeners have read them.

First Attempt
Have messages with a limited TimeToBeReceived value. Use PeekNext
instead of Receive to walk through the queue.
Failed because System.Messaging doesn't expose the PeekNext method
available to VB/C++.

Any suggestions?

Jonathan Allen

 

[Nick Malik]

why not write your own multi-way delivery point. E.g. create an endpoint
app that reads the queue and then resends messages according to topic to
two, three, four, etc, dedicated queues, one for each topic. Your existing
end point app can simply listen to the topic that they choose.

That shouldn't be that hard to do.

--- Nick

 

[Jonathan Allen]

why not write your own multi-way delivery point.

I'm lazy. Since the clients may connect or disconnect (sometimes without
warning), I will have to manage queue creation and have a heartbeat monitor.
Still, it looks like that may be the best route.

Jonathan

 

[Kris]

I cant answer if MSMQ can be accessed like JMS Topics. But it is easy to
access BEA's JMS Topic. Obviously you can't access it directly, but you
could expose a webservice from Weblogic that would access this JMS Topic and
from your .NET client, you could access the Weblogic's WebService.

Also check out COM+ Queued Components. I am guessing that they might provide
Topic based funcitonality with COM+ Components.

 

[Jonathan Allen]

Thanks,

Jonathan

I cant answer if MSMQ can be accessed like JMS Topics. But it is easy to
access BEA's JMS Topic. Obviously you can't access it directly, but you
could expose a webservice from Weblogic that would access this JMS Topic and
from your .NET client, you could access the Weblogic's WebService.

Also check out COM+ Queued Components. I am guessing that they might provide
Topic based funcitonality with COM+ Components.