Eclipse Community Forums: BIRT » Can't get 2.0 Releases Preview to Work ... Stumped and Pulling My Hair Out

Home » Archived » BIRT » Can't get 2.0 Releases Preview to Work ... Stumped and Pulling My Hair Out

Can't get 2.0 Releases Preview to Work ... Stumped and Pulling My Hair Out [message #113783]

Tue, 24 January 2006 02:29

Eclipse User

Originally posted by: pcasey.earthlink.net

I installed 2.0 Release over 2.0 RC 1 by following the upgrade install.
I started eclipse with -- clean.
The report perspective comes up just fine.
I can make a new report.
I can preview data (jdbc connection works and polls data).
When I hit preview though, I get:

HTTP Status 500 -

------------------------------------------------------------ --------------------

type Exception report

message

description The server encountered an internal error () that prevented it
from fulfilling this request.

Which tells me absolutely nothing. There's nothing in the internal eclipse
log. If the Birt viewer is producing a log, I can't find it. I thought
updating the web.xml in :

\eclipse\plugins\org.eclipse.birt.report.viewer_2.0.0\birt\W EB-INF

To turn on debugging via:

<context-param>
<param-name>BIRT_VIEWER_LOG_DIR</param-name>
<param-value></param-value>
</context-param>


<context-param>
<param-name>BIRT_VIEWER_LOG_LEVEL</param-name>
<param-value>FINEST</param-value>
</context-param>

But I'm still not getting a log out.

Can anybody suggest a way to get some debugging informaiton out here? The
preview used to work fine in 1.0.1 and 2.0 RC 1, but now all I get is the
aforementioned nondescript error.

Thanks,

--- Pat

Re: Can't get 2.0 Releases Preview to Work ... Stumped and Pulling My Hair Out [message #113826 is a reply to message #113783]

Tue, 24 January 2006 02:48

Eclipse User

Originally posted by: pcasey.earthlink.net

Managed to solve part of the problem; BIRT now has additional third party
dependencies; when they say you need to install axis on the install page,
they're not kidding.

Other noteworthy changes:

Previously (1.0.1 and 2.0 RC 1) default parameter values were specified with
the javascript tick mark, presumably because they were evaluated by the js
parser e.g.

'ABC123' or
'12/25/05'

That no longer works; you now *must* remove the ticks so

ABC123
12/25/05

I'll pass along more information as I have it.

--- Pat

Previous Topic:	Execution of large report problems
Next Topic:	Carriage returns/line breaks in data

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 27 00:32:01 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter