[
http://jira.jboss.com/jira/browse/JBMESSAGING-806?page=all ]
Tim Fox updated JBMESSAGING-806:
--------------------------------
Summary: Allow JBM client to run in a jnlp (or other) sandbox (was: JBM is
assuming it can look up system properties on the client side)
Issue Type: Task (was: Bug)
Priority: Minor (was: Major)
Allow JBM client to run in a jnlp (or other) sandbox
----------------------------------------------------
Key: JBMESSAGING-806
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-806
Project: JBoss Messaging
Issue Type: Task
Affects Versions: 1.2.0.Beta1, 1.0.1.SP3
Reporter: Tim Fox
Priority: Minor
Fix For: 2.0.0 Beta 1
JBM (JMSRemotingConnection) does several System.getProperties() to get the override bind
address and port. However in a security restricted environment e.g. jnlp or applet this
may not work.
This causes an exception to be thrown and the connection is not created.
Need to catch the exception and set to null.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira