-
1. Re: Signed Jars
starksm64 Mar 21, 2004 12:41 PM (in response to feldgen)I don't have jboss-3.0.6 laying around so I tried using jboss-3.2.3 and signed the default/lib/{jbossha.jar,jboss.jar} and renamed them signed-jboss.jar
signed-jbossha.jar so that they are not being loaded first and this starts up fine.
I also tried renaming the jboss-3.2.3 dist as jboss-3.0.6-bfa and this did not show any different behavior so either its an issue with 3.0.6 or I'm not reproducing the issue. Can you try jboss-3.2.3?
This is on a winxp pro system running:
[starksm@banshee bin]$ java -version
java version "1.4.2_03"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02)
Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode) -
2. Re: Signed Jars
feldgen Mar 22, 2004 12:34 AM (in response to feldgen)Hi scott,
I will try jboss-3.2.3 but this will take some time...I'll post
the results of this test.
Btw, I am using Gentoo-Linux with sun-jdk-1.4.1_05
Regards,
Lutz Feldgen -
3. Re: Signed Jars
feldgen Dec 27, 2004 2:27 PM (in response to feldgen)Hi Scott,
I completely forgot about this posting...
I tested a while and it seems that the complete jboss-path is responsible for that issue. Maybe the classloaders do theirselves to create this error, I will check the used Classloaders and their order of usage...
regards,
Lutz