Shibboleth Developers

[<>]

I’m probably misdiagnosing the error message Java is giving me then; the bytecode loads, but I get the following error message, which I assumed was related to trying to run Java 5 bytecode with Java 6:

 

14:54:15.065 [main] ERROR e.i.m.s.common.config.BaseService - Configuration was not loaded for shibboleth.AttributeResolver service, error creating components.  The root cause of this error was: java.lang.UnsupportedClassVersionError: Bad version number in .class file

 

Given my constant problems keeping things properly endorsed, I wouldn’t be shocked to find out this is another error related to that, so I’ll double check that and then start digging deeper from there.

 

 

From: Nate Klingenstein [mailto:]
Sent: Wednesday, January 30, 2008 3:49 PM
To:
Subject: Re: IDP 2.0 RC1 - src vs. bin

 

Jeff,

 

What JDK are you using that can't load Java 5 bytecode?  We've tested these packages on many Java 5, 6, and 7 JVM's.  Chad will be available tomorrow European time for deeper discussion if it's needed.

 

Thanks,

Nate.

 

On 30 Jan 2008, at 19:58, <> wrote:

What is the intended difference between the src and the bin releases? 

 

I initially downloaded the binary package, but it didn’t work for this first machine, since I am using Java 6 on it (I tested the beta2 with Java 6 without any problems).  When I got java mismatch errors, I realized my mistake and I downloaded the src package, thinking it would be pure source code, and I’d compile everything for Java 6, but it seems like the source release includes binaries for all the associated jars (shibcommon, etc.) that I was expecting to build.

 

It seems like the source package should be everything as source; mixing it with mostly binaries and one component as source doesn’t quite seem to make sense.