|
|
|
|
| Re: how to disable stack trace with BIRT 2.6.1 - confirm steps within please [message #1078150 is a reply to message #1076039] |
Fri, 02 August 2013 15:50   |
 Anthony Farrell
Messages: 29
Registered: August 2012 |
Junior Member |
|
|
Got the source, and have build the viewer, org.eclipse.birt.report.viewer plug.
There seems to be two types of stack trace data.
Missing Report design file:
Where you specify a report design file that does not exist, if I add the following I ensure there no stack trace on screen. Can some comment if this is the best place to put this update?
package org.eclipse.birt.report.utility.BirtUtility.appendErrorMessage
...
// start of change
message = "";
// end
out.write( message.getBytes( "UTF-8" ) );
out.flush( );
out.close( );
}
Secondly, other errors, internal to reports, the errors and stack traces are embedded in the HTML report send back to the client browser.
so far I have tracked this down to the following Java file org.eclipse.birt.report.engine.executor.ExecutionContext and the following fields hold the execptions and errors that occurred.
/**
* A list of errors in time order, it is also shared by the report content
*/
private List<EngineException> errors = new ArrayList<EngineException>( );
/**
* The exception list grouped by the element
*/
protected HashMap<DesignElementHandle, ElementExceptionInfo>
elementExceptions = new HashMap<DesignElementHandle, ElementExceptionInfo>( );
What is the best way to ensure these exceptions and stack traces are not send back to the browser, should I simply modify setter methods to set the stack track data to an empty string, OR could some point me to the code that generates the HTML and I can modify this.
|
|
|
|
Powered by
FUDForum. Page generated in 0.03853 seconds
] 
Search
Help
Register
Login
Home
