Using the SDK Author Editor with Java Web Start

Post here questions and problems related to oXygen frameworks/document types.
sderrick
Posts: 264
Joined: Sat Jul 10, 2010 4:03 pm

Using the SDK Author Editor with Java Web Start

Post by sderrick »

We are using the SDK editor as applet to access a CMS document repository and it is working great.

However, since Chrome(Google) is at war with Java and removed all NPAPI support, and the possibility that Mozilla may follow suit, I was considering packaging the Editor into a java application and running it with Java Web Start and exit the browser wars.

I'll have to move my HTML5/Javascript code that is the web page wrapper for the Applet into the java application but it may be worth it. 3 of our users normally use chrome and all had issues getting Safari/JRE configured correctly to run the applet. Every time we have a new user it seems like its a crap shoot on whether the applet is going to run with problems or not. And the problems are usually getting the browser setup correctly.

Any body doing this with great success or failure?

Does Java Web Start run as problem free as Oracle says it does?

Any gotchas to watch for?

thanks,
Scott
Radu
Posts: 9051
Joined: Fri Jul 09, 2004 5:18 pm

Re: Using the SDK Author Editor with Java Web Start

Post by Radu »

Hi Scott,

I'm not sure what the future of Java applets and JavaWebstart application will be. Unfortunately this is not something we can control.
If you want to test how JavaWebstart works in different browsers, you can use our JavaWebstart demo (it starts Oxygen XML Editor from a web browser):

https://www.oxygenxml.com/javawebstart.html

It seemed to work for me in Chrome on Windows. A while back when I tested there were problems running it on Mac OSX with Safari which just downloaded the file descriptor but did not start it.

Another approach for you would be to use our WebApp:

https://www.oxygenxml.com/webapp/

which is 100% Javascript on the client side and has the Java part on the server side. We built it as a future replacement for the applet, because unfortunately browsers seem to be heading in a direction of not supporting (at least by default) Java applets.

Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
Post Reply