Kedar Mhaswade wrote:
> Tim,
> Thank you. Two questions:
>
> - If this is *generated* stuff -- shouldn't it go to "generated" folder?
> Alternatively, we already have a folder for each application. If that
> app is jws-enabled, isn't it a good idea to create "java-web-start"
> folder inside that application's folder? There are some benefits of
> doing this, in a scenario that does not apply to GlassFish yet :)
this is not generated, this is an administrator manual step to put it there.
I don't want to overload the application folder as it opens the door to
in place
modification of the application's folder which we don't support.
>
> - Is this (going to be) documented?
>
I hope so :)
Jerome
> Thanks,
> Kedar
>
> Tim Quinn wrote:
>
>> Kedar,
>>
>> We need a way to serve a signed version of an application's generated
>> app client jar file for Java Web Start launches of an app client. If
>> an app client needs permissions beyond the Java Web Start sandbox
>> permission set in order to run correctly, then Java Web Start
>> requires that the jar be signed. The
>> .../domains/<domain-name>/java-web-start/<app-name> directory is
>> where we ask the administrator to deposit the signed version of the
>> generated app client jar file so we can download it to end-user
>> systems during a JWS launch.
>>
>> These directories are created during deployment.
>>
>> - Tim
>>
>> Kedar Mhaswade wrote:
>>
>>> Recently, I observed that we have a java-web-start directory that
>>> gets created
>>> in <domain-config-directory>. When does this directory get created and
>>> what is the purpose of the same?
>>>
>>> Kedar
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>