-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Yeah, because queues and topics are so non-dynamic, it seems to me
that using a messageSelector is really the only way to get much
practical use out of JMS. It's very non-OO, but it's working for me.
Check out
http://java.sun.com/j2ee/j2sdkee/techdocs/api/javax/jms/Message.html
for details on the syntax of the messageSelector. Let me know if I
can help you out.
> -----Original Message-----
> From: Michael Hustler [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 26, 2001 3:25 PM
> To: Jboss (E-mail)
> Subject: [JBoss-user] Filtering JMS Messages
>
>
> I have read in a different thread of 3 ways to create
> temporary Topics. 2
> of these are non-portable and the 3rd one is limited such
> that the message
> consumer must be created by the topic creator or something like
> that.
>
> I am looking for a way to reduce the total potential message
> flow in the
> system by filtering the message delivery. My Message Consumers
> will typically be able to specify information used to reduce the
> number of messages that are delivered to them:
> - publisher identity
> - finer granularity of message type (determined at runtime)
> - attribute values
>
> I want to be able to determine this filtering at runtime
> instead of in the
> deployment descriptor.
>
> I have been trying to read-up on "MessageSelector", but I
> can't find any
> documentation on how to apply this in an J2EE environment.
>
> Can anyone guide me in the right direction?
> Thanks,
> -mike.
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>
iQA/AwUBOujgadUPOr8a7vy5EQJZ/wCfc41BfYn2AcW8pmyjfF6p3otH1PgAnR0K
ZYiI9SLmsUSftpj9hMM0T8cv
=7unx
-----END PGP SIGNATURE-----
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
