OpenSAML user discussion

[Chad La Joie <>]

Complain to Sun about non-intuitive error messages?  ;)

Usually this error is thrown when:
 - You have a serialized version of a class and try to read it in to a
different version of that class (for example one that has had some
fields removed).

 - Some sort of bytecode instrumentation has screwed up the class
bytecode...  but not so badly as to be unusable.

 - And, i think, when a class instance is loaded by one class loader and
then passed to a different loader that contains a different version of
the class.

Now, the bad part is that I suspect your not knowingly doing any of
these.  Can you provide the URL of the metadata you trying to load?
I'll see if I can replicate the error.

Paul Hethmon wrote:
> Ok, so I put together a little test application to try this out:
> 
>  
> 
> …
> 
> fbmd = new FileBackedURLMetadataProvider(url, 60000, file);
> 
> fbmd.setParserPool(parser);
> 
> fbmd.initialize();
> 
> …
> 
>  
> 
> Assume everything is declared ok, I'm getting a strange exception:
> 
>  
> 
> Exception in thread "main" java.lang.IncompatibleClassChangeError
> 
>   at
> org.opensaml.saml2.metdata.provider.AbstractMetadataProvider.unmarshallMetadata(AbstractMetadataProvider.java:159)
> 
>  
> 
> which is the parsing line in the code. With the rest of the stack trace
> going back to the initialize() line.
> 
>  
> 
> Googling didn't turn up any obvious things I might have set up wrong and
> generally my environment seems to work ok with everything else I've used
> in the OpenSAML libraries.
> 
>  
> 
> Solutions? Suggestions?
> 
>  
> 
> thanks,
> 
>  
> 
> Paul
> 
>  
> 
>  
> 
> Paul Hethmon
> 
> 
> 
> www.clareitysecurity.com
> 
> cell: 865.250.3517
> 
> work: 865.769.0456
> 
>  
> 

-- 
Chad La Joie             2052-C Harris Bldg
OIS-Middleware           202.687.0124