Info on java webstart

hi i have been interested in java webstart but i can only find information expalining what it is not how to use it. the literature that i read stated that you can run a java program from a single click from a website and not much else. i assume that you have to do more than just put a link the executable jar file? if so can you give me a link that shows how to use it please.

>
when you day a step learning curve how hard is it?>It depends on the application,
- if it is 'one jar with no natives' it might be relatively simple.
- another factor is whether the code needs to be digitally signed.
If you are familiar with code signing already, that should not be a problem. Or it will also not be a problem if this app. can run entirely sandboxed, like a common applet, though that is unusual for an average desktop app. that needs to access the the local file system, etc.. Even in that case, it is possible to have a sandboxed (unsigned) app. that can access the local disks, but you need to use the JNLP API, rather than the usual JFileChooser and File classes.
What is your app.? What sort of things does it do?
Another factor is just how many of the little 'added extras' of webstart you would like to use for the app. Shortcuts and menu items, a splash screen and icons for the app. and shortcuts etc. - these are all specified in the JNLP file that actually launches the application.
And to answer an earlier question, instead of linking to the main jar, a JWS launch would link to the JNLP file. The JNLP file specifies all the resources, shortcuts etc. as well as the main class.
To make sure the necessary Java is in place (before the user clicks the link to the JNLP), Sun provides the [deployJava.js|https://jdk6.dev.java.net/deployment_advice.html] which you can use on the site that links to the application launch file.

Similar Messages

PI 7.1 ESR and Java Webstart very slow

Hi,
I have been using the PI ESR and IB on the snow leapord OS with Mozilla and Safari browsers. The java webstart seems to be very slow and working on the ESR objects is sometimes a pain as it takes long time to save , activate or change and sometimes I end up java heap space issues although we are running at a 2 gig heap size. Is it only me or is anyone else facing the same issue?
Is it time to go back to good old windows XP? or can this be fixed in Mac ...I love my Mac for other reasons though...:)
Teresa

Hi,
>>>serverXXXPI71
add this server info with related IP address into your hosts file
and it will work
Regards,
Michal Krawczyk

Error with Java WebStart Signed Jars on 1.6.0_19's new Mixed Code

All,
First, we have a valid code signing certificate/keystore from Thawte that works for signing webstart jars as of update 18. For some reason, if you run our webstart application on update 19 JRE, the runtime believes that some of the jars are not signed and some are. Even though we create and sign the jars in the exact same way and after inspecting the jar the JRE believes are not signed they have the necessary signing entries/files in the manifest folder. Not sure why the signing process would work for some of our jars and not for others. There is nothing really all that different.
So, because the JRE believes some of the jars are not signed the new security warning "...contains both signed and unsigned code." pops up ( [Error Description|http://java.com/en/download/help/error_mixedcode.xml] ). If I press yes, then I get the following exception.
java.lang.SecurityException: trusted loader attempted to load sandboxed resource from https://path-to-our.jar
     at com.sun.deploy.security.CPCallbackHandler$ParentCallback.check(Unknown Source)
     at com.sun.deploy.security.CPCallbackHandler$ParentCallback.access$1400(Unknown Source)
     at com.sun.deploy.security.CPCallbackHandler$ChildElement.checkResource(Unknown Source)
     at com.sun.deploy.security.DeployURLClassPath$JarLoader.checkResource(Unknown Source)
     at com.sun.deploy.security.DeployURLClassPath$JarLoader.getResource(Unknown Source)
     at com.sun.deploy.security.DeployURLClassPath.getResource(Unknown Source)
     at java.net.URLClassLoader$1.run(Unknown Source)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(Unknown Source)
     at com.sun.jnlp.JNLPClassLoader.findClass(Unknown Source)
     at java.lang.ClassLoader.loadClass(Unknown Source)
     at java.lang.ClassLoader.loadClass(Unknown Source)
     at main.JwsMain.main(JwsMain.java:32)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at com.sun.javaws.Launcher.executeApplication(Unknown Source)
     at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
     at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
     at com.sun.javaws.Launcher.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)If I press "no" I get the following exception (I get this exception if I try to run our WebStart application with no signed jars as well, no warnings about missing certs, just straight to error)
java.lang.NullPointerException
     at com.sun.deploy.cache.CachedJarFile.findMatchingSignerIndices(Unknown Source)
     at com.sun.deploy.cache.CachedJarFile.entryNames(Unknown Source)
     at com.sun.deploy.cache.DeployCacheJarAccessImpl.entryNames(Unknown Source)
     at com.sun.deploy.security.CPCallbackHandler.assertTrust(Unknown Source)
     at com.sun.deploy.security.CPCallbackHandler.access$700(Unknown Source)
     at com.sun.deploy.security.CPCallbackHandler$ParentCallback.check(Unknown Source)
     at com.sun.deploy.security.CPCallbackHandler$ParentCallback.access$1400(Unknown Source)
     at com.sun.deploy.security.CPCallbackHandler$ChildElement.checkResource(Unknown Source)
     at com.sun.deploy.security.DeployURLClassPath$JarLoader.checkResource(Unknown Source)
     at com.sun.deploy.security.DeployURLClassPath$JarLoader.getResource(Unknown Source)
     at com.sun.deploy.security.DeployURLClassPath.getResource(Unknown Source)
     at java.net.URLClassLoader$1.run(Unknown Source)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(Unknown Source)
     at com.sun.jnlp.JNLPClassLoader.findClass(Unknown Source)
     at java.lang.ClassLoader.loadClass(Unknown Source)
     at java.lang.ClassLoader.loadClass(Unknown Source)
     at main.JwsMain.main(JwsMain.java:32)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at com.sun.javaws.Launcher.executeApplication(Unknown Source)
     at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
     at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
     at com.sun.javaws.Launcher.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)Does anyone know why this would be happening? It only occurs with the new update. We use the same keystore and process for signing all of our jars so it really doesn't make since why some of them work and some of them don't. Also, our JNLP is correct or it wouldn't work in update 18.
Edit: We've tried it on Windows XP SP3 and compiled the code using update 18 and used jarsigner both from 18 and 19 with same results.
Edited by: chenthor on Apr 1, 2010 8:44 AM
Edited by: chenthor on Apr 1, 2010 8:51 AM

Hi All,
So we've been battling this bug for a year or so now, and I've come up with a solution to the webstart bugs
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6967414
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6805618
(see the bugs for more details)
From what we can tell the bug stems from the way that the jar signers information is "cached" by webstart.
When a jar is loaded by webstart, it is represented by a CachedJarFile instance. When loading and using classes the signature for the jar is verified. The signers used is the one that is stored in the CachedJarFile instances. These "signers" are stored as SoftReferences. SoftReferences are like WeakReferences, except that they only become eligible for garbage collection when there is a small amount of available heaps space remaining and that the object is only softly reachable. (That's a pretty crude description, but it will do for now)
So what we found was happening is that when the JVM reached a certain heap size threshold and needed to allocate more heap, that these soft references (and hence the signers information) werebeing garbage collected. if you attempt to load a class after this you get the security error.
So I came up with a hack to work around this. At application startup, iterate through all of the CachedJarFile objects on the classpath and create a hard reference to each of the signers info by putting them in a static list somewhere. From our tests this seems to work. (though with the intermittent nature of the problem, it has been hard to prove conclusively, though we've had some success repro-ing the issue, by reducing the intial heap size and using VisualVM to watch for heap expansions and forcing gc's)
Below is the code for the hack, to run it just call JarSignersHardLinker.go() and it will do some sanity checks (running on webstart on java 1.6 update 19 or higher) before spawning a new thread to create hard refs for all signers info for all jars on the classpath.
import java.io.IOException;
import java.lang.ref.SoftReference;
import java.lang.reflect.Field;
import java.lang.reflect.InvocationTargetException;
import java.lang.reflect.Method;
import java.net.JarURLConnection;
import java.net.URL;
import java.net.URLConnection;
import java.util.ArrayList;
import java.util.Enumeration;
import java.util.LinkedHashSet;
import java.util.List;
import java.util.Set;
import java.util.jar.JarFile;
* A utility class for working around the java webstart jar signing/security bug
* see http://bugs.sun.com/view_bug.do?bug_id=6967414 and http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6805618
* @author Scott Chan
public class JarSignersHardLinker {
    private static final String JRE_1_6_0 = "1.6.0_";
     * the 1.6.0 update where this problem first occurred
    private static final int PROBLEM_JRE_UPDATE = 19;
    public static final List sm_hardRefs = new ArrayList();
    protected static void makeHardSignersRef(JarFile jar) throws java.io.IOException {
        System.out.println("Making hard refs for: " + jar );
        if(jar != null && jar.getClass().getName().equals("com.sun.deploy.cache.CachedJarFile")) {
             //lets attempt to get at the each of the soft links.
             //first neet to call the relevant no-arg method to ensure that the soft ref is populated
             //then we access the private member, resolve the softlink and throw it in a static list.
            callNoArgMethod("getSigners", jar);
            makeHardLink("signersRef", jar);
            callNoArgMethod("getSignerMap", jar);
            makeHardLink("signerMapRef", jar);
//            callNoArgMethod("getCodeSources", jar);
//            makeHardLink("codeSourcesRef", jar);
            callNoArgMethod("getCodeSourceCache", jar);
            makeHardLink("codeSourceCacheRef", jar);
     * if the specified field for the given instance is a Softreference
     * That soft reference is resolved and the returned ref is stored in a static list,
     * making it a hard link that should never be garbage collected
     * @param fieldName
     * @param instance
    private static void makeHardLink(String fieldName, Object instance) {
        System.out.println("attempting hard ref to " + instance.getClass().getName() + "." + fieldName);
        try {
            Field signersRef = instance.getClass().getDeclaredField(fieldName);
            signersRef.setAccessible(true);
            Object o = signersRef.get(instance);
            if(o instanceof SoftReference) {
                SoftReference r = (SoftReference) o;
                Object o2 = r.get();
                sm_hardRefs.add(o2);
            } else {
                System.out.println("noooo!");
        } catch (NoSuchFieldException e) {
            e.printStackTrace();
            return;
        } catch (IllegalAccessException e) {
            e.printStackTrace();
     * Call the given no-arg method on the given instance
     * @param methodName
     * @param instance
    private static void callNoArgMethod(String methodName, Object instance) {
        System.out.println("calling noarg method hard ref to " + instance.getClass().getName() + "." + methodName + "()");
        try {
            Method m = instance.getClass().getDeclaredMethod(methodName);
            m.setAccessible(true);
            m.invoke(instance);
        } catch (SecurityException e1) {
            e1.printStackTrace();
        } catch (NoSuchMethodException e1) {
            e1.printStackTrace();
        } catch (IllegalArgumentException e) {
            e.printStackTrace();
        } catch (IllegalAccessException e) {
            e.printStackTrace();
        } catch (InvocationTargetException e) {
            e.printStackTrace();
     * is the preloader enabled. ie: will the preloader run in the current environment
     * @return
    public static boolean isHardLinkerEnabled() {
         boolean isHardLinkerDisabled = false; //change this to use whatever mechanism you use to enable or disable the preloader
        return !isHardLinkerDisabled && isRunningOnJre1_6_0_19OrHigher() && isRunningOnWebstart();
     * is the application currently running on webstart
     * detect the presence of a JNLPclassloader
     * @return
    public static boolean isRunningOnWebstart() {
        ClassLoader cl = Thread.currentThread().getContextClassLoader();
        while(cl != null) {
            if(cl.getClass().getName().equals("com.sun.jnlp.JNLPClassLoader")) {
                return true;
            cl = cl.getParent();
        return false;
     * Is the JRE 1.6.0_19 or higher?
     * @return
    public static boolean isRunningOnJre1_6_0_19OrHigher() {
        String javaVersion = System.getProperty("java.version");
        if(javaVersion.startsWith(JRE_1_6_0)) {
            //then lets figure out what update we are on
            String updateStr = javaVersion.substring(JRE_1_6_0.length());
            try {
                return Integer.parseInt(updateStr) >= PROBLEM_JRE_UPDATE;
            } catch (NumberFormatException e) {
                //then unable to determine updatedate level
                return false;
        //all other cases
        return false;
      * get all the JarFile objects for all of the jars in the classpath
      * @return
     public static Set<JarFile> getAllJarsFilesInClassPath() {
          Set<JarFile> jars = new LinkedHashSet<JarFile> ();
         for (URL url : getAllJarUrls()) {
             try {
                 jars.add(getJarFile(url));
             } catch(IOException e) {
                  System.out.println("unable to retrieve jar at URL: " + url);
         return jars;
     * Returns set of URLS for the jars in the classpath.
     * URLS will have the protocol of jar eg: jar:http://HOST/PATH/JARNAME.jar!/META-INF/MANIFEST.MF
    static Set<URL> getAllJarUrls() {
        try {
            Set<URL> urls = new LinkedHashSet<URL>();
            Enumeration<URL> mfUrls = Thread.currentThread().getContextClassLoader().getResources("META-INF/MANIFEST.MF");
            while(mfUrls.hasMoreElements()) {
                URL jarUrl = mfUrls.nextElement();
//                System.out.println(jarUrl);
                if(!jarUrl.getProtocol().equals("jar")) continue;
                urls.add(jarUrl);
            return urls;
        } catch(IOException e) {
            throw new RuntimeException(e);
     * get the jarFile object for the given url
     * @param jarUrl
     * @return
     * @throws IOException
    public static JarFile getJarFile(URL jarUrl) throws IOException {
        URLConnection urlConnnection = jarUrl.openConnection();
        if(urlConnnection instanceof JarURLConnection) {
            // Using a JarURLConnection will load the JAR from the cache when using Webstart 1.6
            // In Webstart 1.5, the URL will point to the cached JAR on the local filesystem
            JarURLConnection jcon = (JarURLConnection) urlConnnection;
            return jcon.getJarFile();
        } else {
            throw new AssertionError("Expected JarURLConnection");
     * Spawn a new thread to run through each jar in the classpath and create a hardlink
     * to the jars softly referenced signers infomation.
    public static void go() {
        if(!isHardLinkerEnabled()) {
            return;
        System.out.println("Starting Resource Preloader Hardlinker");
        Thread t = new Thread(new Runnable() {
            public void run() {
                try {
                    Set<JarFile> jars = getAllJarsFilesInClassPath();
                    for (JarFile jar : jars) {
                        makeHardSignersRef(jar);
                } catch (Exception e) {
                    System.out.println("Problem preloading resources");
                    e.printStackTrace();
                } catch (Error e) {
                     System.out.println("Error preloading resources");
                     e.printStackTrace();
        t.start();
}

Java Webstart in Windows 7

I have a Java Webstart application running on a Windows 7 Laptop. An Apache Tomcat webserver is also installed on this laptop so everything is self contained. When the laptop is not connected to a network and I start the application, Webstart gives me two instances of the application. When the laptop is connected to a network, I get one instance.
I also have an identical installation on a Windows Vista PC. Irrespective of whether or not this PC is connected to a network, I always get one instance of the application when I start it.
I would like to hear from anyone who has noticed similar behaviour and whether they have an explanation and whether they can advise if this is a 'bug' or a 'feature'.

Thanks a lot for your reply.
but no luck. still nothing happens.... javaws just dies without logging anything?
maybe its a security problem?
here is the system event log again:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-10-01T18:41:12.000000000Z" />
<EventRecordID>3719</EventRecordID>
<Channel>Application</Channel>
<Computer>XXXXXX</Computer>
<Security />
</System>
- <EventData>
<Data>javaws.exe</Data>
<Data>10.7.2.10</Data>
<Data>503d8a47</Data>
<Data>javaws.exe</Data>
<Data>10.7.2.10</Data>
<Data>503d8a47</Data>
<Data>c0000417</Data>
<Data>00011d9c</Data>
<Data>16c0</Data>
<Data>01cda004542d62eb</Data>
<Data>C:\Program Files (x86)\Java\jre7\bin\javaws.exe</Data>
<Data>C:\Program Files (x86)\Java\jre7\bin\javaws.exe</Data>
<Data>92310d7c-0bf7-11e2-bd20-6cf049e5f1f7</Data>
</EventData>
</Event>
Edited by: 962394 on 01.10.2012 11:44

Jar files download problems in Java Webstart with JRE 1.6

We have encountered a few problems in Java Webstart with JRE 1.6
In JRE 1.5, the jar files are getting downloaded onto the client
machine with it's original names.
Example :
Server File Name : acm.jar
Client File Name : RMacm.jar
But in JRE 1.6, the jar files are getting downloaded with improper file names.
Example :
Server File Name : acm.jar
Client File Name : 4fb074cc-66fc7407
Moreover the path itself seems to be invalid.
Example Path :
JRE 1.5 path:
C:\Documents and Settings\Administrator\Application
Data\Sun\Java\Deployment\cache\javaws\https\D17.16.23.11\P443\DMtest\DMwebStart
JRE 1.6 path:
C:\Documents and Settings\Administrator\Application
Data\Sun\Java\Deployment\cache\6.0\12
Due to this, we are facing Classpath problems.
What changes do we have to make to the code, for Java
Webstart to work ?
We are using JBoss 4.0.4 and JDK 1.5 in the Server
On the client machine, we have IE 6 and JRE 1.6.01
Help would be appreciated.

Ask your Java Web Start question at:
http://forum.java.sun.com/forum.jspa?forumID=38

Java webstart proxy bypass not working

java webstart does not work through proxy as the jar files is not getting downloaded. most simple solution would of course be to bypass the proxy for the target server (by entering the server in the system network preference panel). however, that does not work. apparently this bypass is not taken into account by java webstart.
if i remember correctly there once was a possibility to set such things (proxy etc.) in java webstart preferences. this is not existing any more.
how can i solve the problem?
tia
tobias (very desperate)

Hi,
Thanks a lot for your reply, Prateek.
I have already checked SAP Note 1142580 - "Java Proxy is not processing messages in parallel" where they ask to modify the ejb-jar.xml. However, on performing the change in ejb-jar.xml and while building the EAR, I get the following error:
Error! The state of the source cache is INCONSISTENT for at least one of the request DCs. The build might produce incorrect results.
Then, on going through the SAP Note 1142580 again, I realised that the SAP Note 1230721 also should be looked onto which will be needed for generating the Java proxy from Message Interfaces in IR for parallel processing.
Kindly help me if any of you have worked on such a scenario.
Thanks in advance,
Regards,
Rosie Sasidharan.

The steps to enable Java Webstart in OSX Mavericks are not working.

The steps located here: http://support.apple.com/kb/ht5559 are not re-enabling the Java Webstart for Java 6 in OSX Mavericks. I have tried all four steps about 20 times and looked at all the settings in all my browsers (chrome, safari, and firefox) and all say "missing plugin" when I go to any website that requires Java -- in this case, the NY Times Crossword Puzzle's "solve with a friend", which is incompatible with Java 7 so upgrading does not help me. I've tried searching for other answers and all keep directing me to the same four steps that have not worked.
A note, those steps worked when I had the same problem after upgrading to Mountain Lion. Should something be altered for Mavericks?
Please advise.

You'll possibly need to remove Oracle Java altogether before, see these notes on their WebSite:
http://www.java.com/en/download/help/mac_uninstall_java.xml
After you remove it, go through the steps to re-enable Apple Java again; and, inside Safari, you can also go to its menu and choose "Reset Safari".
Hope this helps.

How to use Java WebStart with EJB ?

hi forum...
how to use Java WebStart with EJB ? examples ?
thanks
mindu

Greetings,
hi forum...
how to use Java WebStart with EJB ? examples ?Well, for starters these are complementing, not 'cooperating', technologies. I presume, since EJB's do not - directly, at least - communicate with a web browser, that you intend for "Java WebStart" to somehow invoke an EJB?? Java WebStart is a technology for running client-side (Java) applications from the web browser - perceptively, the application resides on the server, but technically it, like an applet, is downloaded to the client and run there. Unlike an applet, however, it is not constrained by "sandbox" restrictions and does not have to be re-downloaded each time it is invoked - though the process allows for automagically updating the client-side with new versions of the application. ;) So, with this in mind, to "use Java WebStart with EJB" means little more than deploying an EJB client application with Java WebStart as the distribution channel.
thanks
minduRegards,
Tony "Vee Schade" Cook

Why Do We Need Java Webstart For XI

Hi All,
Can Any Body Please Explain me Why We Need Java Webstart For XI.
What is the Use of it in XI.
Please Let me Know
Regards
Babu

Java web start is a technology by Sun Microsystems which enables running thick clients developed in Java after they are downloaded from the server and / or cached on the local drive...
XI IR & ID are thick clients developed in Java which communicate with the XI server using EJB based communication and Java web start makes it possible to download / cache them and trigger point to run them...more on Java web start here -->
http://java.sun.com/developer/technicalArticles/WebServices/JWS_2/JWS_White_Paper.pdf

Servlet Communication with Java WebStart

Hi there,
we have an application that works fine with Java WebStart whenever we start it in a local area network. But from outside the LAN the application cannot communicate to it's servlets. I use the codebase IP address with the servlet runner's port (http://<codebase IP>:port/) as URL for servlet communication, but the application's request never reaches the servlets.
My question is now, if anyone had the same or a similar problem with servlet communication using Java WebStart, or if anyone knows, if that might be a problem with proxy configuration.
The servlet runner we use, is JServ from Sun (JSDK2.0) and the webserver where it is running on is not behind a firewall or a proxy, but the client PC with the web start application is.
Thanks,
Katja

Thank you for your early reply. But I think, that's not the problem.
I get no security error and the webserver is identified the same way it is in the jnlp file. Also my application is not running in the Sandbox. My assumption is, that the http-request to the servlet does not go through the proxy server between my PC and the PC the servletrunner is running on.
I wonder if I have to configure my application to use a proxy server for communication with the servlets instead of the direct http-request to the servlet runner?

How to launch a Java WebStart application with older JREs when Java 7u25 is on the client?

How can I launch older versions of my Java WebStart application, that are built and run with Java 7u21 or earlier, even if Java 7u25 is installed locally on the client? Application launch and behaviour must be reliable and consistent.
Background:
As of 7u25 (and later), Java Webstart applications launch with a different class loader than pre-7u25.
My Java Webstart application has supported versions that were built with older versions of the JDK (e.g. Java 5, 6, 7u21 or earlier). These applications run with their required JRE version, enforced through JNLP. Once Java 7u25 is installed locally, these older applications fail to launch, due to classloader differences.
The question is: what is required to run older Java WebStart applications even if 7u25 (or later) Java Webstart is installed locally on the client?

I confirm your findings when using shortcuts to try specific versions of JavaWS with 7u25 or later installed:
JRE 5u14 launched and the classloader was as pre 7u25
JRE 6u43 would not launch
JRE 7u21 launched but the classloader was not as pre 7u25
You can launch the shortcut with the JavaWS -verbose option to display a messagebox with valuable information.
I am keeping a close watch on this thread.

Java 6 Update 12 64bit Java Webstart documentation

I notice that 64bit 6 Update 12 comes with 64bit version of Java Webstart - I am just wondering whether there are any documentation on how 64bit Java Webstart works? For example:
1) By default it will use the 64bit JRE to launch an application. What if an JNLP embedded some 32bit JNI DLLs that requires the use of 32bit JRE?
2) How can an app specify larger heap if it runs on 64bit host, but less on a 32bit host?
3) Is there any new extensions to JNLP to support 64bit Java?
Thanks.

1.) The initial release of the 64 bit version of javaws will work only with 64 bit JRe's. There is no support yet for mixing.
2.) You can specify different dlls for use with 64 bit and 32 architectures just as you can with operating systems as follows:
<resources>
<java version="1.6+"/>
<jar href="myapp.jar" main="true"/>
<resources os="Windows" arch="i586">
<nativelib href="mydll32.jar"/>
</resources>
<resources os="Windows" arch="amd64">
<nativelib href="mydll64.jar"/>
</resources>
</resources>
3.) There are no new JNLP extensions.
/Andy

Accessing Java WebStart files

Hi all,
I have setup Java WebStart for all of our projects so clients can just go to the server web page, find a link and then click and launch the program they want. I am running a Glassfish server on a Linux box and can only get to the files on localhost. If I try to access the files remotely, I get Permission Denied, 403.
Is there a special configuration for Glassfish that is restricting remote users from getting files? I can get whatever file I want locally (http://localhost:8082/resource/file%3a/webstart/Project.jnlp, including the jars), but when I try to get them remotely, that is when Glassfish says Permission Denied and I have nothing in the logfiles that say what is going on.
On a sidenote, how would I access those files relative to the JAR I deployed? My JAR is at /website and I can get to /website/index.jsp, but not /website/Project.jnlp so my workaround is to use the resource configuration.
Walter

If the first jar file is an executable jar file (you run it via the command "java -jar whatever.jar"), then classes in it will not be able to load classes from other jar files unless you explicitly name those jar files in the "classpath" line of the executable jar file's manifest.

Java WebStart does not launch at all.

Some one help me!!
I have spend one whole day trying to figue out whats going on.
I have a JNLP file like this
<?xml version="1.0" encoding="utf-8"?>
<jnlp spec="1.0+" codebase="http://it-106/jws_ws" href="jws_basic.jnlp">
<information>
<title>Test Application</title>
<vendor>Test GmbH</vendor>
<homepage href="http://www.test.com"/>
<description>Test Appliaction for Java Webstart</description>
<icon href="images/cervision.jpg"/>
<offline-allowed/>
</information>
<security>
<all-permissions/>
</security>
<resources>
<j2se version="1.4+ 1.3+ 1.2+"/>
<jar href="jws_basic.jar"/>
</resources>
<application-desc main-class="JWSMain_Basic"/>
</jnlp>
Then when I start my application via webstart
it gives the following error
An error occurred while launching/running the application.
Category: Launch File Error
The following required field is missing from the launch file: <jnlp>
My application works perfectly well with
java -jar jws_basic.jar
Can some one help me whats going on.
Note, my mime type if set for jnlp
Thanks in advance
Guneshwar

Some of us are still stupid too....what did you do? :D

Download Error in java webstart

Hi
I am getting a error while downloading application from java webstart
I am using Apache 2.2 http server running on port 80
In that in htdocs folder I have placed my jnlp file and my jar file
My jnlp file is like this .
All file are in the folder htdocs/products/
<jnlp spec="1.0+" codebase="http://127.0.0.1/" href="/products/note.jnlp">
<information>
<title>My Application </title>
<vendor>ABC Pvt Ltd</vendor>
<homepage href="http://127.0.0.1/products/"/>
<description>Sample Test</description>
<shortcut>
<desktop/>
<menu submenu="My Application 2.0 (web)"/>
</shortcut>
</information>
<security><all-permissions/></security>
<resources>
<j2se version="1.4+" />
<jar href="/products/Notepad.jar" main="true" download="eager"/>
</resources>
<application-desc main-class="Notepad">
</application-desc>
</jnlp>
The error which i am getting is
An error occurred while launching/running the application.
Title: My Application
Vendor: ABC Pvt Ltd
Category: Download Error
Bad MIME type returned from server when accessing resource: http://127.0.0.1/products/note.jnlp - text/plain
JNLPException[category: Download Error : Exception: null : LaunchDesc: null ]
at com.sun.javaws.cache.DownloadProtocol.doDownload(U nknown Source)
at com.sun.javaws.cache.DownloadProtocol.isLaunchFile UpdateAvailable(Unknown Source)
at com.sun.javaws.LaunchDownload.getUpdatedLaunchDesc (Unknown Source)
at com.sun.javaws.Launcher.downloadResources(Unknown Source)
at com.sun.javaws.Launcher.handleApplicationDesc(Unkn own Source)
at com.sun.javaws.Launcher.handleLaunchFile(Unknown Source)
at com.sun.javaws.Launcher.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Please help ...
How to solve this issue .
But the same file is working in Tomcat Server
please let me know
Thank you
Prakash

Bad MIME type returned from server..A server should return a content type of..
application/x-java-jnlp-file for JNLP
files.
Tomcat probably does that by default, but
other servers might need to be told about it.
See your server help, for how to set a
content-type.

Info on java webstart

Similar Messages

Maybe you are looking for