Re: Long shot on a IllegalAccessError

[Thorbjoern Ravn Andersen <ravn@xxxxxxxxxx>]

Den 01/05/10 22.16, Pete Helgren skrev:
> I DID see this once, even in my Windows environment, but it seemed to
> stem from a mismatch in Birt versions.  I have checked and rechecked the
> jars and both environments seem to match.  Unless the jars are cached
> somewhere on the i, I don't think a version mismatch is the issue.
>
>    
From the javadoc:
===

Thrown if an application attempts to access or modify a field, or to 
call a method that it does not have access to.

Normally, this error is caught by the compiler; this error can only 
occur at run time if the definition of a class has incompatibly changed.

====

In your situation that _could_ make sense as the i JVM caches some of 
the work hidden with the jar file in the IFS.  I have seen that 
overwriting the contents of a jar file did not remove that work.  I 
would start with removing the birt jar completely from the ifs and copy 
it in again.

On second thought.  Do it with all your jars :)
> I could use *any* ideas you might have.  I don't quite understand what
> is being accessed illegally here.  Not much in the Birt method
> ExtensionManager.initialize() to go on.
>    
I've also seen it happen with reflection I think.  Nasty one there.