"timfox" wrote : I'm not sure which version you are looking at but the
socket transport, which is the default in 1.0.x, requires tcp connections to be made back
to the client, making it unsuitable for clients running in some kind of sandbox, e.g. jnlp
or applets, where the security policy will typically not allow this.
|
| 1.2 will introduce a bisocket transport which doesn't require connections to be
made back to the client. The bisocket is not available in 1.0.x
Tim,
Thanks for the reply. I'm not sure thats the problem as the jnlp grants jars full
access. Furthermore the exception isn't generated on the socket creation, but on
accessing the system property. I could be missing something though.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010063#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...