applet - Problems with deployment, advice needed for a web-based java application -

i have developed command-line (read: no gui) java application crunches through numbers based on given dataset , series of parameters; , spits out series of html files resultant reports. these reports hold large amount of data in tables, in order give users easy , quick overview of results, utilized jung2 library , created nice graph.

here's gets interesting; since graph interactive should deployed after application has run , files generated, whenever user wants view reports. decided go applet based deployment, not happy current setup due following reasons:

1. i want make software simple use possible (my users won't tech-savvy, , tech-intimidated in cases). distribute 1 jar only, forced me put applet else needs in package in same jar main application.

2. the applet , main application need communicate results, create xml-based report used hold information. long files on local machine , not moved around works fine. unfortunately need files moved around. user should able take "results" folder usb stick, go anywhere plug stick computer , able use report he/she likes.

for time being applets implemented following html code:

<applet code="package.myapp.visualization.graphapplet.class"          codebase="file:/home/user/myapp"          archive="myapp-0.2.6-r28.jar"          width="750" height="750">     <param name=input value="results/test_name/results.fxml"> </applet> 

as can see applet not work if parent folder moved location.

---

as far know have couple of alternatives:

a) change codebase point url on our webserver put jar file. creates problem permissions, applet not able read results file. alternative upload results file server when user wants visualize graph, although not sure if that's option due server security , if made upload happens automatically without bothering user.

b) can use relative path on codebase attribute, whole folder hierarchy needs intact upon copy. last resort, if cant come better way it.

c) change deployment method (would avoid alternative not spend more time on development phase)

any ideas? missing something? how tackle problem? thanks,

i'm not sure entirely understand use-case, understand, suggest this:

dump applet application launched using java web start. have jnlp file declare file association fxml file type. when user double clicks fxml file, passed argument main(string[]) of jws application.

a sand-boxed jws application can gain access resources on local file system using jnlp api. here demo. of jnlp api file services.