Implementation of jnlp://

Mon May 1 12:26:48 UTC 2017

Yes, the ITW message management is much better than JWS.

I've tried to build from sources and it works as expected. There is an 
issue in javaws.desktop.in, it should be in:
MimeType=x-scheme-handler/jnlp;x-scheme-handler/jnlps

Is possible to cross-compile from Linux the Windows dist without the 
plugins: Here are my parameters:
./configure --prefix=/home/nicolas/opt/IcedTea-web 
--with-jdk-home=/usr/lib/jvm/java-8-oracle --disable-native-plugin

An the plugins with cross-compilers like mingw-w64?

Best,

Nicolas

On 28. 04. 17 14:44, Jiri Vanek wrote:
> On 04/25/2017 06:52 PM, Nicolas Roduit wrote:
>> In my opinion this feature is major against the slow death of the 
>> Java client side although its implementation is very simple. It 
>> offers the possibility to launch an application from many contexts 
>> (browsers, mail client...).
>
> Agree.
>
>>
>> For some advanced applications, we still believe that running a Java 
>> client application is the good choice (easy deployment, performance, 
>> maintainability).
>>
>> However, since  JRE 8_121  I'm disappointed about the security 
>> behaviors of JWS. I've filled out a bug at 
>> https://bugs.openjdk.java.net/browse/JDK-8175981 but the guys from 
>> Oracle consider as a "security" feature.  As I don't have the 
>> permission to post a comment, I can only think that Oracle is killing 
>> the dynamic behavior of JWS. Hopefully, this issue doesn't appear 
>> with the new jnlp protocol.
>
>
> I'm afraid yours hopes are invalid.  Those checks are here,and really 
> are annoying.  Itw had adapted them on its own way, and so it have its 
> own ways how to get rid of it (more levels or 
> verbosity/security/checks, different mechanism on remembering of 
> already clicked yes/no (based on regex, so you can get rid of a lot)
> In 1.6 this was little bit glued together, in 1.7 this was rewritten. 
> You can even redirect "YES\nYES\nYES..." to stdin of javaws to walk 
> around it completely :))
>
>>
>> I've seen that the version 1.7 will have a windows experimental 
>> version. It would be nice if a future version of the IcedTea-web 
>> could install the mechanism for the jnlp handler (on Windows it is 
>> very simple).
>
>
> Indeed it will have windows support. In all cases, it will be heavily 
> experimental as my windows abilities are very limited.  In all cases 
> it will be some beggining, andhopefuly the windows port will grow in 
> right direction.
> The binary release of ITW for windows will not be capable of 
> registering the protocol (no msi, just zip), however any 
> redistributor, will be bale to pack this blob and wrap to msi or 
> whatever suitable. (note, this may change, it is still some way to 
> walk before release)
>
> Also src release of ITW dont have any url registrations, but to RPM 
> for fedora I'm maintaing, I will add it (thank you for hints)
>
>
> HtH
>   J.
>>
>> Best,
>>
>> Nicolas
>>
>> On 25. 04. 17 15:19, Jiri Vanek wrote:
>>> On 04/24/2017 05:39 PM, Nicolas Roduit wrote:
>>>> Hi Jiri,
>>>>
>>>> You can try with the link "Non square pixels"  at 
>>>
>>> TY!
>>>
>>>> https://dcm4che.atlassian.net/wiki/display/WEA/DICOM+Samples
>>>> Note: In some browsers, the jnlp handler doesn't work if you copy 
>>>> directly the link in the URL bar 
>>>> (jnlp://launcher-weasis.rhcloud.com/weasis-pacs-connector/viewer?studyUID=2.16.756.5.5.100.397184556.14391.1373576413.1508). 
>>>
>>>
>>>
>>>
>>> ugh. indeed. the protocol registration appeared pretty tricky. I 
>>> tried 5 browsers, and if it worked, it had sidekicks. Anyway, your 
>>> example worked for me.
>>>
>>> The change is so simple that it may bebackported to 1.6. Still, with 
>>> 1.7 on way(it was supposed to release in February, but got stuck on 
>>> translations), I would rather wait. How critical is this for you?
>>>
>>>>
>>>>
>>>> To configure the jnlp handler on Linux, see the end of this page: 
>>>> https://docs.oracle.com/javase/9/deploy/overview.htm
>>>>
>>>> For making other examples, you only need to replace the scheme of a 
>>>> jnlp link (http => jnlp).
>>>
>>> Yup. I had several self testing implementations, but nothing beats 
>>> real life.
>>>>
>>>> Best,
>>>>
>>>> Nicolas
>>>>
>>>> On 24. 04. 17 16:47, Jiri Vanek wrote:
>>>>> On 04/24/2017 10:49 AM, Jiri Vanek wrote:
>>>>>> On 03/08/2017 08:18 PM, Nicolas Roduit wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> Is there any plan in IcedTea-Web to follow this implementation: 
>>>>>>> https://bugs.openjdk.java.net/browse/JDK-8055464 ?
>>>>>>>
>>>>>>> It should help a lot for having a better integration of JWS with 
>>>>>>> most of browsers.
>>>>>>>
>>>>>>> Best regards,
>>>>>>>
>>>>>>> Nicolas
>>>>>>>
>>>>>> Up to now, There were no intentions.
>>>>>>
>>>>>>
>>>>>> Now I will take a look, but can not promise.
>>>>>>
>>>>>
>>>>>
>>>>> Today I made a patch for this. Are you able to test it? As I 
>>>>> myself dont have any examples of this, it would be extremely useful!!
>>>>>
>>>>> Tahnx!
>>>>>
>>>>>  J.
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20170501/37f690eb/attachment-0001.html>