If you’re a developer using Crystal Reports for Eclipse (CR4E) for your reporting component, this blog entry will be of interest to you. I’ll discuss. SAP (Business Objects) has recently released Crystal Reports for Eclipse it as a separate package known as CR4E, which contains Crystal Reports for Java. Eventually you will get: JVM terminated. Exit code=1 /usr/bin/java -Xms40m – Xmxm -jar /home/msiegel/CR4E/download/eclipse/./ -os linux -ws gtk.
|Published (Last):||2 December 2012|
|PDF File Size:||7.75 Mb|
|ePub File Size:||6.21 Mb|
|Price:||Free* [*Free Regsitration Required]|
If debugging was correctly turned on, you should see a Java stack trace just before the X BadMatch. The designer component is available as a plug-in to Eclipse and is used for designing and previewing reports.
This is to eclipe that the documentation remains comprehensible.
– SWT_AWT bridge sometimes crashes on Linux
Can you produce another log? Comment 41 Denis Mikhalkin If you call the methods in the CRJavaHelper class from your application at the same time another thread is accessing the report engine for example, from a viewer a ConcurrentAccessException may be thrown.
Every time a ReportSource is destroyed, the count is decremented. When eclipse instantly disappears from the Linux desktop, this is a major usability and user-confidence problem.
Crystal Reports for Eclipse Reference
Can everyone on this bug report please turn on debugging and help us confirm this? When I click on any of the tabs I get this: The debugging callbacks that SWT sets up may be overridden by AWT’s own X error handlers, which may explain why you have not been able to get a stack trace even if SWT debugging is enabled: I am eclipsw it is something to do with the setup of the CRConfig. The fact that we could get our own error handler from the XSetErrorHandler means that someone first stored our error handler somewhere and then restored it AFTER we exited from our error-handling section.
There are two ways to resolve this problem. I have no idea about the recursion.
Blag’s best blogs picks eclipde New Business Objects forum category: I hooked it to the Display this way: Perhaps when disposing the SWT component should attempt to dispose the nested AWT frame and wait for it to complete before disposing the underlying OS resource? Embedding the component in the Shell led to very few crashes. Comment 61 Steve Northover cg4e However, we do this for atomic X calls – and restore the previous error handler immediately.
Every time a ReportClientDocument opens a report rpt file, the reference count for that report instance is incremented. Comment 70 Mark Siegel Comment 31 Silenio Quarti Unspecified error at org. However, adding new parameters is not supported. Does anyone have a repeatable case? Data displayed on eclipsf report is restricted based on the parameter values supplied to the report, same is programmatically done below: I also have seen the ErrorHandler looping error a few times.
Marking this one fixed as per Steve’s comment Delete the Crystal Reports plug-ins under Eclipse’s Plugin folder.
cr4e relnotes en
Crystal Reports – Product Overview Crystal Reports is delivered in three editions with features added upon with each edition and its core feature diagrammatically depicted in Figure 1. Comment 22 Omry Yadan The program ” received an X Window System error.
I used Eclipse 3. I’ll illustrate using following sample codes for viewing reports on the web, where I keep the ReportSource in session. Note that the CrystalReportViewer instance here is not used for any viewing purpose – it’s instantiated solely to dispose the ReportSource.
Furthermore, this document does not result in any direct or cf4e contractual obligations of SAP. For example, a description field that would export to 21 rows in Crystal Reports may take 23 rows in Crystal Reports for Eclipse.
But it is not critical – program continues working after this exception.
I believe the error was related to the string containing the location of the MS SQL driver in the classpath directive. We are also seeing this error occur sometimes when we are creating our view for the first time. Refer to Eclipse Bugzilla for more details. Can you confirm that the problem doesn’t happen there? Not if I can help on the following error describe the problem.
Our application seems to recover fine from the stack overflow issue, but the application terminates when we get the bad match error. This wizard is used to create a connection profile for the datasource used in the reports.
CallErrorHandler Native Method at sun. The stack trace starts with the following and just repeats itself: Thanks for the log. Comment 15 Omry Yadan