Bugs item #537564, was opened at 2002-03-31 17:24
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=537564&group_id=22866

Category: JBossMQ
Group: v2.4 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Alarik Myrin (alarik)
>Assigned to: Scott M Stark (starksm)
Summary: Support for empty message selectors

Initial Comment:
According to the errata for the JMS specification
(http://java.sun.com/products/jms/errata_051801.html),
empty message selectors should be treated the same as
null message selectors.  

"If the value of a message selector is an empty string,
the value is treated as a null and indicates that there
is no message selector for the message consumer. "

Currently, an empty string message selector within
JBoss 2.4.4 will throw an exception.

This can be fixed by modifying line 45 of
org.jboss.mq.Subscription to read:

      if ( messageSelector == null ||
messageSelector.length()==0) {

instead of:

      if ( messageSelector == null) {

I have also found it helpful to make the following
change to line 46 of org.jboss.mq.selectors.Selector:

InvalidSelectorException exception = new
InvalidSelectorException( "The selector is invalid.: "
+ sel );

...which actually indicates which selector is causing
the trouble, as opposed to indicating simply that "the"
selector is invalid.


----------------------------------------------------------------------

>Comment By: Scott M Stark (starksm)
Date: 2002-04-09 16:54

Message:
Logged In: YES 
user_id=175228

Fixed for the 2.4.5 release

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=537564&group_id=22866

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to