);
sendToActiveMQ(sessionInfo,null);
Hope this helps.
Regards,
Pieter Naaijkens
--
View this message in context:
http://www.nabble.com/Getting-Stomp-support-to-a-usable-state...-tf3858629s2354.html#a11248423
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
- James Strachan [EMAIL PROTECTED] wrote:
...
Just use the JAAS plugin in ActiveMQ and you're good to go; the Stomp
code uses whatever security plugin you're using
As has been discussed, this is broken, and has been since 4.1.1 or earlier.
Is there any sort of roadmap to the ActiveMQ
- PieterN [EMAIL PROTECTED] wrote:
Patch:
---
../../../activemq-snapshot/src/activemq-core/src/main/java/org/apache/activemq/transport/stomp/ProtocolConverter.java
...
I've tried this patch, and it doesn't change anything. Stomp clients can
still connect with any username, and
I've added some documentation about the webconsole and I included a
section about how to password protect it (although only on jetty, but
I hope the folks will figure out how to 'translate'' that to tomcat by
themself :).
And for the JMX-password issue there is a patch by Andrew Deason
- James Strachan [EMAIL PROTECTED] wrote:
On 6/2/07, Tom Samplonius [EMAIL PROTECTED] wrote:
How much more work needs to occur to get Stomp protocol support to
a usable state?
Huh? :) Its very useable right now
James,
Another component of getting Stomp to a usable state, is
On 6/2/07, Tom Samplonius [EMAIL PROTECTED] wrote:
How much more work needs to occur to get Stomp protocol support to a usable
state?
Huh? :) Its very useable right now
The biggest issue is lack of any authentication support for Stomp, so anyone
with access to the Stomp port can get
- James Strachan [EMAIL PROTECTED] wrote:
On 6/2/07, Tom Samplonius [EMAIL PROTECTED] wrote:
How much more work needs to occur to get Stomp protocol support to
a usable state?
Huh? :) Its very useable right now
The biggest issue is lack of any authentication support for
- Tom Samplonius [EMAIL PROTECTED] wrote:
The Web Console has similar issues. There is no easy way to
password protect it. But if you password protect JMX access, it will
break the Web Console.
...
I was wrong here. I based my comment on this bug report:
How much more work needs to occur to get Stomp protocol support to a usable
state? The biggest issue is lack of any authentication support for Stomp, so
anyone with access to the Stomp port can get and send anything. I can't
imagine that anyone is using Stomp in production yet.
But is
