| RWT Test Dependencies [message #135392] |
Mon, 08 June 2009 09:10  |
Eclipse User |
|
|
|
Originally posted by: markus.wolf.nmmn.com
Hi,
is it possible to release the test plugins/fragments along with the RAP/
RWT release? We have a RWT standalone application deployed in a tomcat
and build with maven.
The problem we have now is that we could not use the
org.eclipse.rap.rwt.testfixture from maven, since the released RWT jars
are signed and the testfixture is not signed (we could not sign it with
the proper values). Also we do not want to build all the RWT dependencies
on our own without signing.
Regards
Markus Wolf
--
NMMN - New Media Markets & Networks GmbH
Langbehnstrasse 6, 22761 Hamburg
Geschäftsführung: Kfm. Michael Schütt
Finanzamt HH-Altona - UStID DE 812 699 852 - HRB 71102 Hamburg
HypoVereinsbank - BLZ 200 300 00 - Konto-Nr. 156 29 82
http://www.nmmn.com
Tel.: +49 40 284 118-0 - Fax: +49 40 284118-999
Softwareentwicklung LLynch: -720
|
|
|
| Re: RWT Test Dependencies [message #135542 is a reply to message #135392] |
Mon, 08 June 2009 16:24   |
|
Hi Markus,
> is it possible to release the test plugins/fragments along with the RAP/
> RWT release? We have a RWT standalone application deployed in a tomcat
> and build with maven.
> The problem we have now is that we could not use the
> org.eclipse.rap.rwt.testfixture from maven, since the released RWT jars
> are signed and the testfixture is not signed (we could not sign it with
> the proper values). Also we do not want to build all the RWT dependencies
> on our own without signing.
What exactly is the problem with mixing signed and unsigned jars?
Regards, Ralf
|
|
|
| Re: RWT Test Dependencies [message #135582 is a reply to message #135542] |
Tue, 09 June 2009 09:38   |
Eclipse User |
|
|
|
Originally posted by: markus.wolf.nmmn.com
Hi Ralf,
>> is it possible to release the test plugins/fragments along with the
>> RAP/ RWT release? We have a RWT standalone application deployed in a
>> tomcat and build with maven.
>> The problem we have now is that we could not use the
>> org.eclipse.rap.rwt.testfixture from maven, since the released RWT jars
>> are signed and the testfixture is not signed (we could not sign it with
>> the proper values). Also we do not want to build all the RWT
>> dependencies on our own without signing.
>
> What exactly is the problem with mixing signed and unsigned jars?
>
the problem is the java classloading. I get this exception:
java.lang.SecurityException: class "org.eclipse.rwt.Fixture"'s signer
information does not match signer information of other classes in the
same package
at java.lang.ClassLoader.checkCerts(ClassLoader.java:776)
at java.lang.ClassLoader.preDefineClass(ClassLoader.java:488)
at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
at java.security.SecureClassLoader.defineClass
(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$000(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301 )
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320 )
at org.eclipse.swt.RWTFixture.setUp(RWTFixture.java:160)
at de.nmmn.iscontrol.rwt.modules.snmp.InterfacesPartTest.setUp
(InterfacesPartTest.java:28)
.....
Any idea on how to solve this?
Thanks
Markus Wolf
--
NMMN - New Media Markets & Networks GmbH
Langbehnstrasse 6, 22761 Hamburg
Geschäftsführung: Kfm. Michael Schütt
Finanzamt HH-Altona - UStID DE 812 699 852 - HRB 71102 Hamburg
HypoVereinsbank - BLZ 200 300 00 - Konto-Nr. 156 29 82
http://www.nmmn.com
Tel.: +49 40 284 118-0 - Fax: +49 40 284118-999
Softwareentwicklung LLynch: -720
|
|
|
| Re: RWT Test Dependencies [message #135650 is a reply to message #135582] |
Wed, 10 June 2009 10:09   |
|
Hi Markus,
well, I understand that this problem prevents the use our unsigned test
bundles together with the signed bundles from the release, because they
share some packages. To circumvent this problem you could either:
- Use bundles from CVS for testing. You can also checkout by tag to get
the version you need.
- Try to remove the signature from the signed bundles for testing (I
think you only have to remove some files from the META-INF folder, but
not sure)
- Not sure if there is some command line parameter that prevents the vm
from checking signatures...
You can also file an enhancement request to provide test bundles in the
release, but you'll risk getting a WONTFIX...
Best regards,
Ralf
Markus Wolf wrote:
>>> is it possible to release the test plugins/fragments along with the
>>> RAP/ RWT release? We have a RWT standalone application deployed in a
>>> tomcat and build with maven.
>>> The problem we have now is that we could not use the
>>> org.eclipse.rap.rwt.testfixture from maven, since the released RWT jars
>>> are signed and the testfixture is not signed (we could not sign it with
>>> the proper values). Also we do not want to build all the RWT
>>> dependencies on our own without signing.
>> What exactly is the problem with mixing signed and unsigned jars?
>>
> the problem is the java classloading. I get this exception:
>
> java.lang.SecurityException: class "org.eclipse.rwt.Fixture"'s signer
> information does not match signer information of other classes in the
> same package
> at java.lang.ClassLoader.checkCerts(ClassLoader.java:776)
> at java.lang.ClassLoader.preDefineClass(ClassLoader.java:488)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
> at java.security.SecureClassLoader.defineClass
> (SecureClassLoader.java:124)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
> at java.net.URLClassLoader.access$000(URLClassLoader.java:56)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301 )
> at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320 )
> at org.eclipse.swt.RWTFixture.setUp(RWTFixture.java:160)
> at de.nmmn.iscontrol.rwt.modules.snmp.InterfacesPartTest.setUp
> (InterfacesPartTest.java:28)
> ....
>
>
> Any idea on how to solve this?
> Thanks
> Markus Wolf
|
|
|
| Re: RWT Test Dependencies [message #135662 is a reply to message #135650] |
Wed, 10 June 2009 10:35  |
Eclipse User |
|
|
|
Originally posted by: markus.wolf.nmmn.com
Hi Ralf,
thanks for your answer. We will consider the options but I think its not
that easy for us. Since we are using maven to build our application we
have the local maven repository to resolve dependencies and manipulating
this dependencies only for a test run is not that easy I think.
Maybe we remove the signature entirly from the bundles in our maven-
repository.
Thanks for your hints.
Regards
Markus
> well, I understand that this problem prevents the use our unsigned test
> bundles together with the signed bundles from the release, because they
> share some packages. To circumvent this problem you could either:
>
> - Use bundles from CVS for testing. You can also checkout by tag to get
> the version you need.
>
> - Try to remove the signature from the signed bundles for testing (I
> think you only have to remove some files from the META-INF folder, but
> not sure)
>
> - Not sure if there is some command line parameter that prevents the vm
> from checking signatures...
>
> You can also file an enhancement request to provide test bundles in the
> release, but you'll risk getting a WONTFIX...
>
> Best regards,
> Ralf
>
> Markus Wolf wrote:
>>>> is it possible to release the test plugins/fragments along with the
>>>> RAP/ RWT release? We have a RWT standalone application deployed in a
>>>> tomcat and build with maven.
>>>> The problem we have now is that we could not use the
>>>> org.eclipse.rap.rwt.testfixture from maven, since the released RWT
>>>> jars are signed and the testfixture is not signed (we could not sign
>>>> it with the proper values). Also we do not want to build all the RWT
>>>> dependencies on our own without signing.
>>> What exactly is the problem with mixing signed and unsigned jars?
>>>
>> the problem is the java classloading. I get this exception:
>>
>> java.lang.SecurityException: class "org.eclipse.rwt.Fixture"'s signer
>> information does not match signer information of other classes in the
>> same package
>> at java.lang.ClassLoader.checkCerts(ClassLoader.java:776) at
>> java.lang.ClassLoader.preDefineClass(ClassLoader.java:488) at
>> java.lang.ClassLoader.defineClass(ClassLoader.java:615) at
>> java.security.SecureClassLoader.defineClass
>> (SecureClassLoader.java:124)
>> at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
>> at java.net.URLClassLoader.access$000(URLClassLoader.java:56)
>> at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at
>> java.security.AccessController.doPrivileged(Native Method) at
>> java.net.URLClassLoader.findClass(URLClassLoader.java:188) at
>> java.lang.ClassLoader.loadClass(ClassLoader.java:307) at
>> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301 )
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at
>> java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320 )
>> at org.eclipse.swt.RWTFixture.setUp(RWTFixture.java:160) at
>> de.nmmn.iscontrol.rwt.modules.snmp.InterfacesPartTest.setUp
>> (InterfacesPartTest.java:28)
>> ....
>>
>>
>> Any idea on how to solve this?
>> Thanks
>> Markus Wolf
--
NMMN - New Media Markets & Networks GmbH
Langbehnstrasse 6, 22761 Hamburg
Geschäftsführung: Kfm. Michael Schütt
Finanzamt HH-Altona - UStID DE 812 699 852 - HRB 71102 Hamburg
HypoVereinsbank - BLZ 200 300 00 - Konto-Nr. 156 29 82
http://www.nmmn.com
Tel.: +49 40 284 118-0 - Fax: +49 40 284118-999
Softwareentwicklung LLynch: -720
|
|
|
Powered by
FUDForum. Page generated in 0.01974 seconds