Hi, I recently started using activeMQ 6.1.1, upgrading from an old 5.X version. I'm trying to set the pathSpec to fit my needs for the securityConstraintMapping bean in jetty.xml and have encountered what seems to be a problem with it. It used to accept a comma-separated list of path spec patterns, but now it seems to treat the entire string as one path.
For example, if I try to use this pathSpec string: /admin/*,/api/* ActiveMQ fails to start up, with this error: ...Caused by: java.lang.IllegalArgumentException: Servlet Spec 12.2 violation: glob '*' can only exist at end of prefix based matches: bad spec "/admin/*,/api/*" The asterisk before the comma is considered to be in the middle of one long path. I tried the pathSpec that is shown in /examples/conf/jetty-demo.xml, even in the latest version: /admin,/api/* ActiveMQ does start up, because there's no asterisk in the middle. Then, it allows unrestricted access to /admin and /api/* but asks for a password at the path "/admin,/api/" before saying the path doesn't exist. I'm guessing this was caused by some change in jetty. If so, I don't know if it's a bug over there or something that just needs to be configured differently now... Does anyone have any thoughts? Thanks, Chris The information contained in this email message, including any attachments, is intended solely for use by the individual or entity named above and may be confidential. If the reader of this message is not the intended recipient, you are hereby notified that you must not read, use, disclose, distribute or copy any part of this communication. If you have received this communication in error, please immediately notify me by email and destroy the original message, including any attachments. Thank you. **Hibu IT Code:1414593000000**
