It seems that a STOMP client isn't constrained by the socket security 
policy limitation? Or is it that the debug player isn't constrained.

My app uses an ActiveMQ message system and the public Stomp client. I 
know for sure that a Socket Policy server is not running on the box, 
because I shut it down, yet the messages still come through 
successfully. And I am connecting AFTER I shut down the policy server.

I was expecting a security violation when I shut down the policy 
server.

Can anyone tell me what's going on?

Reply via email to