-
1. Re: Java Web Start
joelvogt Jul 31, 2002 8:12 PM (in response to rakesh_mishra)I've used web-start without any problems at all. You might have to look at the way you are connecting to your interfaces. Any useful errors you can post?
-
2. Re: Java Web Start
epotvin Jan 24, 2003 9:08 AM (in response to rakesh_mishra)I'm happy to see that somebody succesfully get jws working with jboss... because I can't. Maybe you should make some try :
http://machine.dnsalias.org:8080/Fournisseur/jws/FournisseurGUI.html
You'll see what happen in the console when you open the :
Fournisseur - Liste des fournisseurs menu
I know, it's in french, but the error is in english.
Here is a stacktrace part :
java.security.AccessControlException: access denied (java.net.SocketPermission 192.168.0.1:50510 connect,resolve)
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:270)
at java.security.AccessController.checkPermission(AccessController.java:401)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:542)
at java.lang.SecurityManager.checkConnect(SecurityManager.java:1044)
at java.net.Socket.connect(Socket.java:420)
at java.net.Socket.connect(Socket.java:376)
at java.net.Socket.(Socket.java:291)
at java.net.Socket.(Socket.java:119)
and here is my jnlp file :
<?xml version="1.0" encoding="UTF-8"?>
Gestion des fournisseurs
Les consultants Parent et associés inc.
Application servant à gérer les fournisseurs
<j2se version="1.3+" />
<all-permissions/>
<application-desc main-class="org.cpa.system.gui.Client" /> -
3. Re: Java Web Start
petertje Jan 24, 2003 11:11 AM (in response to rakesh_mishra)Did you sign the jar files?
I'm not a jws expert, but it is obviously a security issue and i can image that jws won't let the application connect to the network if it is not trusted....
Hth
Peter. -
4. Re: Java Web Start
cuplan Jan 28, 2003 2:57 PM (in response to rakesh_mishra)I have had a very similar problem and *HAVE* signed my JAR files. It's as if, when I pack the JAR and JNLP up in a WAR so JBoss will serve them up as static content, the JAR's signature becomes ruined.