You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use very complex JNLP files with a huge set of properties like: <property name="myprefix.initialContextFactory" value="org.wildfly.naming.client.WildFlyInitialContextFactory"/>
In the past we had an issue using the default jndi.xxx prefix because the generated -Djndi.xxx commandline was too long.
So we changed to lets say myprefix.xxx
Since 1.10.0 those are not added any more.
We use very complex JNLP files with a huge set of properties like:
<property name="myprefix.initialContextFactory" value="org.wildfly.naming.client.WildFlyInitialContextFactory"/>
In the past we had an issue using the default jndi.xxx prefix because the generated -Djndi.xxx commandline was too long.
So we changed to lets say myprefix.xxx
Since 1.10.0 those are not added any more.
The workaround using deployment.properties mentioned here:
https://board.karakun.com/viewtopic.php?p=10573&sid=072e283934096c0d1e95f20de055344e#p10573
is not applicable. The client machine is not under our control. The jnlp file change and there are a lot of properties used.
This breaks the applications currently when the clients press update OWS on startup.
The text was updated successfully, but these errors were encountered: