Yes, If I run it from outside Tapestry/Jetty/etc, it runs ok.
I mean, It comes with some sample .java to show how to load a report. I used
them to load my reports and it worked ok.
The order of the pentaho's method calls is the same in my app.
Regards !
--
View this message in context:
http://ta
Are you sure tapestry/jetty has anything to do with it? Can you write
a straight java (no webapp/jetty) unit test that loads the file?
On Thu, May 26, 2011 at 1:32 PM, atcach wrote:
> Furthermore, if I open the .xml from an hex editor, I only see the < sign,
> not the BOM for any encoding.
>
Furthermore, if I open the .xml from an hex editor, I only see the < sign,
not the BOM for any encoding.
: 3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d 22 31 .http://tapestry.1045711.n5.nabble.com/T5-Locale-problem-tp4428763p4429973.html
Sent from the Tapestry - User mailing list archive at
The problem is that it is unpacked (a pentaho report is a zip file with many
xml's inside) by the system (running in jetty in linux with utf-8), because
if I unzip it and get the encoding of the xml's I see them ok. But I think
is reencoding them in the middle or something like that. Could it be t
> The prolog is everything that comes before the wrote:
>> My guess of a locale problem is that Caused by:
>> org.xml.sax.SAXParseException: Content is not allowed in prolog. is usually
>> because the "
> The prolog is everything that comes before the at the xml and you can't see anything before
> My guess of a locale problem is that Caused by:
> org.xml.sax.SAXParseException: Content is not allowed in prolog. is usually
> because the " wrote:
> Hi,
> I'm struggling reading a Pentaho Report.
> The report is mainly a jar file with xml's inside.
> If I compile it from outside tapestry it wor
