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 :)
- Is this (going to be) documented?
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
>>