On a server if we save .jnlp file and the jars , they will be available to the clients openly.
Lets say if we have to give the link to jnlp only after login..
I want to give access to .jnlp file to only those people who know the right username and password.
If somewone directly puts the .jnlp link in the browser then it should not be accessible to the user.
In some way the session has to be transfered from jsp application server to webstart.
Does webstart provide any kind of authentication facility??
I doubt it. Why would they bother designing an authentication protocol when the jars are served over HTTP? HTTP already has an authentication protocol you can use.
samrat dhamale
Greenhorn
Joined: Apr 15, 2011
Posts: 9
posted
0
The jar files could be easily converted to java code word by word using reverse engineering tool. Would not want legacy code to be accessible to wrong minds..
Java is not offering inherent capabality to obfuscate code to such a level where reverse engineering is not possible.. We have to use opensource tool..
If we want to distribute code as native OS lets say windows system. There also Java is not providing any inherent facility.
Designers can sit with leisure thinking why on earth people would want to obfuscate their code or distribute native code for Windows.
Java is for platform independence. But what if i want to make my application available only on windows and Mac.
I would want to distribute applications in windows way in windows and Mac way in Mac.
Whole point... Java Designer asking Why would some one want it .. is invalid question.. Need to bring JAVA close to Rapid Application Designing Tool..
0
