Hi Thilo, > Yes, that's a known issue. There is one trick you can use: don't use > InternationalizedException directly, but inherit from it. Bundle > this > exception class with your pear. Since message localization is done > in > the exception class, the correct class loader will then be used and > your message bundle will be found. It's a bit of a hack, but it > works ;-)
Thanks for the fast reply! Is there a bug report listed somewhere? I looked for it, but didn't find anything. Thanks for the workaround. My concern is that since we want to "host" arbitrary annotators from third parties, etc. *their* annotators won't implement the trick and thus fail :( Thanks!!! Kirk
