users@glassfish.java.net

Re: [Java Web Start] GFv3+Eclipse : Build problems

From: <glassfish_at_javadesktop.org>
Date: Tue, 18 May 2010 10:56:50 PDT

Oops, out of bounds... Here is the last part of my previous post :

ONFIDENTIAL. Use is subject to license terms.
--&gt;
&lt;!--
 This client side config file pairs with wss-server-config-1.0.xml on the server
 and supports the following UseCases:
 Usecase 1: Authentication by Protected UsernameToken
 Usecase 3: Encrypted UsernameToken and MessageBody
 Usecase 4: Response Encryption Key Learnt from Incoming Message

 Certificate Alias Information :
 1. A certificateAlias under the &lt;xwss:Encrypt&gt; element signifies the certificate
    of the recipient of the message.
 2. A certificateAlias under the &lt;xwss:Sign&gt; element signifies the certificate of the
    sender.

 NOTE:

   1. the certificateAlias has the above meaning for all the Sign and Encrypt elements below
   2. there are several Sign and Encrypt elements below and similarly several RequireSignature and
      RequireEncryption elements. Which of them would be actually used at runtime will depend on
      the AuthPolicy passed to the module.

      For Example : if Auth-Source=Sender then only the &lt;xwss:UsernameToken&gt; elements will be used
      and none of the &lt;xwss:Sign&gt; elements will be used.
      If Auth-Source=Content then the &lt;xwss:Sign&gt; element will be used

   3. The different variations of &lt;xwss:Encrypt&gt; elements in this configuration file are to accomodate
       default encryption of the UsernameToken.

   4. The actual certificate alias to be used for any Signature operation can be modified during AuthModule
       initialization by setting the alias as the value of &quot;signature.key.alias&quot; property in the Module Options Map.
   5. The actual certificate alias to be used for any Encrypt operation can be modified during AuthModule
       initialization by settin
jnlp file truncated after 10K

----------
Exception :
com.sun.deploy.net.JARSigningException: Détection d'une entrée non signée dans la ressource : file:/D:/gf301b18/glassfishv3/glassfish/domains/domain1/generated/xml/OnlyWebStart/OnlyWebStartClient_jar/OnlyWebStartClient.jar
        at com.sun.javaws.security.SigningInfo.getCommonCodeSignersForJar(Unknown Source)
        at com.sun.javaws.security.SigningInfo.check(Unknown Source)
        at com.sun.javaws.LaunchDownload.checkSignedResourcesHelper(Unknown Source)
        at com.sun.javaws.LaunchDownload.checkSignedResources(Unknown Source)
        at com.sun.javaws.Launcher.prepareResources(Unknown Source)
        at com.sun.javaws.Launcher.prepareAllResources(Unknown Source)
        at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
        at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
        at com.sun.javaws.Launcher.launch(Unknown Source)
        at com.sun.javaws.Main.launchApp(Unknown Source)
        at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
        at com.sun.javaws.Main$1.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)


----------
Console :
#### Java Web Start Error:
#### Détection d'une entrée non signée dans la ressource : file:/D:/gf301b18/glassfishv3/glassfish/domains/domain1/generated/xml/OnlyWebStart/OnlyWebStartClient_jar/OnlyWebStartClient.jar

(translation : unsigned content)

So I'm absolutely unable to start the Main.

I've tried to clear javaws cache (javaws -uninstall), but nothing different occured.

Thanks a lot
[Message sent by forum member 'laps']

http://forums.java.net/jive/thread.jspa?messageID=470316