CaptainCasa
Power User
Joined: 21/11/2007 12:23:06
Messages: 5520
Offline
|
If defining client parameters in the JNLP file and if defining a client parameter value so that it contains a "%"-character, then there is a security exception coming up, so that these parameters are ignored. - There's not a lot information about this in the web, besides a bug report that was sent to Oracle on this... (https://community.oracle.com/thread/3587381)
Luckily the normal parameter values are not containing "%"-characters... But there are some special ones, e.g. various parameters in which you can pass BGPAINT defintions. And here some percentage definition is quite normal (e.g. "rectangle(0,0,100%,100%,...)").
We now added some preprocessing of parameter values into the Swing and the FX client. Whenever a sequence "@@xx@@" is found, then "xx" is interpreted as decimal representation of a unicode character. So if you want to pass "%" then you have to pass "@@37@@".
Please do not ask us, how proud we are about this pre-processing... It's ugly... but we have to bypass the strange behavior...
Next Monday's update will contain the fix. In urgent cases: please contact us and we'll prepare some interim update. - And, just to point out: all this is only relevant for you, if one of your JNLP parameters contains a "%" character!
Regards, Björn
|