Yes, I think this should work.
You will need to use a file:// url rather thand a http:// one.
Also you will not be able to use the IJC URLs feature, as this requires deployment to a servlet compliant web server.
The project deployment was designed for web based deployment, along with all the deployment featrues such as Java Web Start, and IJC URLs.
It was not really designed for deploying via shared files, with these happen to work because they can also be specified as a URL of the file: type.
So a file picker does not really make much sense here.
I think you shoudl be able to get around this just by sending people the correct file URL to use so that they can copy and paste it.
You may not have designed it that way, but I think that in our case where we have a network file system, it will work quite well. Certainly the addition of shared projects is a big improvement. Previously, the requirement for each user to connect to the database server and supply a username and password for both the database and IJC was quite complex. If you could, additionally, preconfigure the license file location, that would be one more complexity removed (as far as the standard user is concerned).
Personally, I am yet to be a convert to java webstart applications. One of the problems I have is losing the URL that points to them. If the application is installed on my hard disk, I can usually navigate to find it in my 'Applications' folder!
have you looked at the InstantJChem java webstart application? It actually copies the java code to your local folder and places an icon on the desktop - much like installing IJC using the windows installer. In my setup, the license file is also copied to the local drive from the server and the entire application can be used offline - again, much like IJC installed using the windows installer. In fact, the two versions are functionally identical from what I can see.
PS good to see another Aust user!
Tim ChemAxon personnel
Joined: 05 Oct 2004
Correct. The 2 versions are identical.
Albeit that deploying using JWS allows some extra things that can only really make sense in that environment e.g IJC URLs and deploying a license file as part of the JWS config.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum