Programmatically check if emitter is installed? [message #236037] |
Fri, 20 April 2007 16:55  |
Eclipse User |
|
|
|
Originally posted by: dan.dan.com
Hi all,
Any one know of a way to tell whether an emitter (such as the pdf emitter)
is installed programmatically? In other words, I'd like to detect the
emitter is not there and give a friendly message back if it's not there.
Instead of trying to generate the report and getting this exception back:
EngineException: org.eclipse.birt.report.engine.api.EngineException: Report
engine fails to create extension to handle this request.
I'd like to not just catch the exception because from the message, it looks
like it could mean other errors too, not just that the emitter is not found.
Thank you for the help, Dan
|
|
|
|
Re: Programmatically check if emitter is installed? [message #236405 is a reply to message #236154] |
Mon, 23 April 2007 16:46  |
Eclipse User |
|
|
|
Originally posted by: jasonweathersby.alltel.net
BTW if you are using the engine api you can use the follows methods to
get info on the available emitters.
String[] eo = engine.getSupportedFormats();
EmitterInfo[] ei = engine.getEmitterInfo();
Jason
Jason Weathersby wrote:
> You could use the plugin registry to see what plugins implement the
> org.eclipse.birt.report.engine.emitters extension point, but this will
> not cover the case for PDF because it can fail because of a missing
> iText lib directory. Hopefully this will not be an issue when 2.2 is
> released. It should could include iText.
>
> Jason
>
> dan wrote:
>> Hi all,
>> Any one know of a way to tell whether an emitter (such as the pdf
>> emitter) is installed programmatically? In other words, I'd like to
>> detect the emitter is not there and give a friendly message back if
>> it's not there. Instead of trying to generate the report and getting
>> this exception back:
>>
>> EngineException: org.eclipse.birt.report.engine.api.EngineException:
>> Report engine fails to create extension to handle this request.
>>
>> I'd like to not just catch the exception because from the message, it
>> looks like it could mean other errors too, not just that the emitter
>> is not found.
>> Thank you for the help, Dan
>>
|
|
|
Powered by
FUDForum. Page generated in 0.07086 seconds