On 08 Feb 2011, at 17:19, Jonathan Levinson wrote: Hi Jonathan
> Thanks for the help! We are not running Eclipse or SWT. > > Here is a fuller log of the exception. Can you see anything wrong with what > we are dong? Thanks! It doesn't seem like you're doing anything wrong from a FOP perspective. Consider that an UnsatisfiedLinkError means that the Java VM cannot locate the native-language definition of a method that was declared 'native' in the source. As FOP itself does not define any native methods, and AFAIK, it does not call any native methods either (not sure if AWT even exposes these in the public API), the issue seems to be located in the Open VMS AWT implementation. One thing to try to get a more accurate picture of which call in FOP ultimately triggers the issue in Open VMS, you could try setting the log level to TRACE or DEBUG. Right now, with INFO level, we can only see that it happens right after the default page-dimensions have been set from the user-config. That leaves font- and image-setup, but one could tell that solely from the fact that it's AWT-related... Regards, Andreas --- --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
