Well, as per JMS spec, JBoss Messaging lets you set the client id
programmatically after creating a connection, and you can define and set
selectors when creating a consumer.
However if you're using MDBs it's different, bear in mind MDBs are not part of
JBM, they're part of the app server, and
OK, thanks again for all your help. I'll post over there and see what I can dig
up.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4232480#4232480
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4232480
Posted: http://www.jboss.org/index.html?module=bbop=viewtopict=155809
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4232488#4232488
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4232488
I think I can use Tim's suggestion (if I can find a way to assign the selector
outside the ear).
Something like:
clientID is NULL AND feed in ('feed1', 'feed2')
| OR
| clientID = 'myClientID' AND feed in ('feed1', 'feed2')
So is there a way for me to assign the clientID other than in the
I don' t understand what you are trying to achieve... mainly here:
anonymous wrote : - I need to be able to also (re)send a notification to only
one client
Can you try abstracting your business and explain what you are trying to
achieve in pure JMS terms?
View the original post :
Sure (and thanks so much for your help!).
I have what amounts to a store-and-forward system (let's call it the SAF for
this discussion). It feeds multiple client systems. The SAF receives a number
of files from different, external systems, which it stores and makes available
via HTTP. The
I think you need a Topic with subscribers and selectors for the regular
day-to-day operation.
And you also probably need a request mechanism on receiving the initial
information. Maybe the client creates a temporary queue, send a request to
receive the initial information, and the initial
If you want a topic subscriber to receive all messages of a certain type and
also receive all messages sent directly to it, can't you assign each subscriber
an id and use a selector like:
| messageType='FOO' OR destinationID=myid
|
View the original post :
clebert:
Thanks for the pointer, I've checked out the sample and started to look it over.
timfox:
If I deploy my app in an .ear file, wouldn't I have to muck around with the
embedded deployment descriptors in each client in order to assign the unique
IDs? I would love to be able to modify the
timfox wrote : If you want a topic subscriber to receive all messages of a
certain type and also receive all messages sent directly to it, can't you
assign each subscriber an id and use a selector like:
|
|
| | messageType='FOO' OR destinationID=myid
| |
It's a good idea but I
I guess I'm not understanding what the user is trying to achieve here.
Also I don't understand why the selector needs to be dynamic. The id is the
client id which can be in the deployment xml.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4232017#4232017
Thank you guys for your help here!
timfox: Is there a way to specify the selector outside of the .ear file? I'm
hesitant to require that the deployer of my application unzip the ear, change
an ID, and rezip it. I would rather use a identical application package on our
production and test
I would use a topic and subscribers (durable if is the case) with selectors.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4231759#4231759
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4231759
That's where I was headed...
I need to be able to also (re)send a notification to only one client
(preferably using the same mechanism). I had thought I could have a selector
that looks for my notifications of interest and/or notifications with a
property set to the client's ID, but I don't
14 matches
Mail list logo
