nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

CLI - Emitter Selection possible?

hendriksti

Dear all, 
 
I'm currently puzzled on how to use the native excel emitter plugin(1) with BIRT runtime 4.2.2 via the command line interface. 
 
When I designed the report (in juno, using the latest BIRT release), I simply placed the jar-File of the emitter in the eclips/plugins-directory. Now using the runtime the emitter is not used, even though I placed the jar-file in the lib-directory and added it to the class path. 
 
My goal is primarily to have the content spread on different excel worksheets. It works in the designer, but not in the runtime. 
 
My call currently looks like this: 
 
<pre class='_prettyXprint _lang-auto _linenums:0'>
java -cp '<many-jar-files>' -DBIRT_HOME='<correct-home>' -Dorg.eclipse.datatools_workspacepath='<workspace-dir>' org.eclipse.birt.report.engine.api.ReportRunner -o '/tmp/out.xls' -f 'xls' -p dbURL=jdbc:postgresql://127.0.0.1:5432/<database> -p dbUsername=<user> -p dbPassword=<password> -p <some-parameters> --emitter_id=org.eclipse.birt.report.engine.emitter.nativexls '/tmp/test.xls.rptdesign'
</pre>
 
I tried it with and without the --emitter_id-parameter. 
 
Where can I start debugging? 
 
Kind regards, 
 
Hendrik 
 
 
--- 
 
(1) <a class='bbc_url' href='http://code.google.com/a/eclipselabs.org/p/native-excel-emitter-birt-plugin/'>http://code.google.com/a/eclipselabs.org/p/native-excel-emitter-birt-plugin/</a> - latest version as of Oct 2011

Find more posts tagged with

Comments

Yaytay

What happens when you do that command?
Do you get built in emitter output or do you get an error?

Jim

Yaytay

I don't think there is an "emitter_id" argument for ReportRunner, so I hunk it's completely ignoring your attempt to set it. 
There is, however, a renderOption argument, and you can specify the emitter ID as a render option. 
Something like: 
<pre class='_prettyXprint _lang-auto _linenums:0'>
--renderOption "emitterID=blah"
</pre>
 
That's based on a bit of googling and the following pages: 
<a class='bbc_url' href='http://eclipsesrc.appspot.com/jsrcs/org.eclipse.birt.report.engine/src/org/eclipse/birt/report/engine/api/ReportRunner.java.html'>http://eclipsesrc.appspot.com/jsrcs/org.eclipse.birt.report.engine/src/org/eclipse/birt/report/engine/api/ReportRunner.java.html</a> 
<a class='bbc_url' href='http://help.eclipse.org/indigo/index.jsp?topic=/org.eclipse.birt.doc.isv/engine/api/org/eclipse/birt/report/engine/api/RenderOption.html'>http://help.eclipse.org/indigo/index.jsp?topic=/org.eclipse.birt.doc.isv/engine/api/org/eclipse/birt/report/engine/api/RenderOption.html</a> 
 
Jim

hendriksti

Thank you for your replies, Jim. 
 
I always get output, an excel file with nearly correct content, but it's all on one worksheet, not three, as it's supposed to be. 
 
I tried setting the parameter the following ways: 
 
<pre class='_prettyXprint _lang-auto _linenums:0'>
-r "emitterID=org.eclipse.birt.report.engine.emitter.nativexls"
--renderOption "emitterID=org.eclipse.birt.report.engine.emitter.nativexls"

-r "IRenderOption.EMITTER_ID=org.eclipse.birt.report.engine.emitter.nativexls"
--renderOption "IRenderOption.EMITTER_ID=org.eclipse.birt.report.engine.emitter.nativexls"

-r "EMITTER_ID=org.eclipse.birt.report.engine.emitter.nativexls"
--renderOption "EMITTER_ID=org.eclipse.birt.report.engine.emitter.nativexls"
</pre>
 
I also tried changing the quotation marks from double to single, I added quotation marks around the value of the emitterID, but to no avail. 
 
What bugs me most is, that I do not get any debug output, I cannot see, whether the parameter name is wrong, or the emitter class cannot be found... is there a way to make the BIRT runtime a little more verbose?

Yaytay

Of those options the first two are the only ones I'd expect to work (and it's the second that I'd be trying).

Look at the output file (open it in notepad++, or similar) if it's a binary file then you have used the right emitter, if it's an XML file then you haven't.

Jim

hendriksti

<blockquote class='ipsBlockquote' data-author="'Yaytay'" data-cid="115131" data-time="1363605099" data-date="18 March 2013 - 04:11 AM">
Look at the output file (open it in notepad++, or similar) if it's a binary file then you have used the right emitter, if it's an XML file then you haven't. </blockquote>
 
Okay, it's XML - so the native emitter was not used in any of my scenarios. Can I somehow modify the report design to enforce the emitter selection? I know, that would be a very ugly hack, but for the time being... or are there other possibilities I'm currently missing?

Yaytay

You can try modifying the RenderOptions in the beforeRender script (or beforeFactory) for the report.
I'm not sure that'll work, or what will happen if you ask for HTML output and then set the emitter ID to the XLS emitter, but you could try it.

I have had success setting other RenderOptions in beforeRender:
reportContext.getRenderOption().setOption("ExcelEmitter.SpannedRowHeight", 2);

Jim

hendriksti

I tried the following (the code went into the beforeRender-Script): 
 
<pre class='_prettyXprint _lang-auto _linenums:0'>
importPackage(Packages.java.util.logging);

var fileHandler = new FileHandler("/_dev/loggia/birt.log", true);
var rootLogger = Logger.getLogger("");
rootLogger.addHandler(fileHandler);

Logger.getAnonymousLogger().info( reportContext.getRenderOption().getEmitterID() );
reportContext.getRenderOption().setEmitterID( "org.eclipse.birt.report.engine.emitter.nativexls" );
Logger.getAnonymousLogger().info( reportContext.getRenderOption().getEmitterID() );
</pre>
 
and when I run my code with the -r "emitterID=..."-option, the first log output is "...prototype.excel" - so the CLI-parameter is not regarded. The second log output is the string set in the line before. But that does not change the output at all - still XML. 
 
My last resort would be to implement a plain java wrapper that is customized towards the native xls emitter and "manually" goes through the process of the report creation - but that is a rather big step to take...