[Passing data between reports]

Don't forget also to define an input control for the parameter of your 2nd report even if it will be never prompted. Without that, the parameter of your invoked report will be "null".

[net.sf.jasperreports.engine.JRException: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException]

Other people have already got this trouble. One of them said that the trouble could be fixed by adding the plugin "XML and Schema". I did it and that fixed my problem.

Do a search on this forum with "UTF-8" and I think you will retreave all the threads about that.

With the next release (iReport NB 3.1.2) I get a similar problem but the fix seems not to work. For the moment, I consider this new release as unusable.

[Troubles using IE and the ajax based repoExplorer]

Hello,

I don't know if it is the same kind of problem, but when I started using Jasperserver I first used as object names French names with accent (é,è,..) and I got troubles : jasperserver seemed to be unable to recognize them. So I stopped to use French accentued words as names and all was right.

For the labels, there is no problem.

For your info

Gaby

[Troubles using IE and the ajax based repoExplorer]

Hello guys,

This morning, for the 1st time ,I tried to access my jasperserver site with IE from another PC than mine (on my PC I use only Firefox) and I was surprised to see that some hyperlinks inside raports were not working and lead me to the login page.

After search, it seemed to be due to some cookies and the level of control of IE.

In the Confidentiality tab, after clicking on "Sites", I added the network domain of my server (which is hosted at a distant provider site) in the trusted domains and after that all was working well.

So , perhaps it is not the same kind of trouble in your case, but have a look about the filtering options of IE and try a test with no control at all.

Hope this helps

Gaby

 edit : sorry I didn't see your last post and that you tried to change IE security parameters

Post Edited by Gabriel Entressangle at 11/27/08 12:50

["SAX exception" IReport 3.1.2 for 3.1.1 report]

I put this reply in order to have this post at the top of the topic list.

Can any people of iReport team tell me if I am the only one to get this problem?

At now, I cannot use iReport 3.1.2 since as soon as I edit a jrxml file already existing, I cannot run it after.

Thanks for your answers!

[Error upgrading to JS 3.1]

I don't fully understand the mechanism between the context.xml and jasperserver.xml files. As far as I remember, the updates done in the context.xml files do not affect tomcat which is based on the $HOMETomcat/conf/Catalina/localhost/jasperserver.xml file. What I do (as far as I remember) is :

- stop Tomcat

- modify context.xml

- delete $HOMETomcat/conf/Catalina/localhost/jasperserver.xml

- restart Tomcat

The context.xml file is copied as $HOMETomcat/conf/Catalina/localhost/jasperserver.xmlwith the updates

[No Oracle jdbc class for iReport 3.1.2]

The suggestion of Luis is better than mine. Now, I remember :  I think that I did as Luis says to add oracle driver and not by copying directly in the directory.

[Parameter is not prompting]

Did you create an "input control" with the same name as your parameter ?

[Invalid byte 2 of 4-byte UTF-8 sequence: 3.1.1]

In fact, the modules you download from internet are somewhere (I don't exactly remember where but I saw them) on your machine connected to internet. Perhaps you can copy them on the other and have to "activate" them through the same menu "Plugin" ( list of loaded modules) but without needing to be connected.

[No Oracle jdbc class for iReport 3.1.2]

Try to put the oracle jdbc jar (ojdbc14.jar)  under :

C:\Program Files\JasperSoft\iReport-nb-3.1.2\ide8\modules\ext

I didn't test but for iReport 3.1.1 it's working so

Post Edited by Gabriel Entressangle at 11/25/08 20:25

[value null]

Rosa,

In SQL, a null value is not equivalent to a "zero" value and the reaction of iReport is normal.

If you want that a null value be considered as a "zero" value, you can use in your SQL the nvl function :

SELECT nvl(FIELD, FIELD,0) which will return ( we suppose that FIELD is numeric) else FIELD (if not null) else 0

If FIELD is a string you write : SELECT nvl(FIELD, FIELD,'') where ''(two single quotes) is the empty chain which is different from the null value for the database.

 

[Parameters in ORDER BY]

I don't know what is the exact content of your "$P{pSequence} but if there are strings, I fear that the expansion which takes care of type adds some quots.

Try using "$P!{pSequence} (notice the "!")which will expand the parameter as is.

Hope this helps

[Using parameters with Oracle 9i]

You wrote

"symbol = $P(symbol)"

In fact, if you wrote exactly like that   it's wrong : the parameter usage is : $P{xxx}

So you have to write : "symbol = $P{symbol}"  (with brackets and not parenthesis)

[Invalid byte 2 of 4-byte UTF-8 sequence: 3.1.1]

Hello,

I also got this trouble. If you do a search on this forum you will find some posts about that.

Just to say that one people gave a work-around : load the plugin-module : "XML and schema" from the "Plugin" menu and this will upgrade iReport in the good way. I did it and it was OK for me.

You can also see on this forum (previous pos) that I have encountered the same kind of error when migrating from 3.1.1 to 3.1.2 and the work-around doesn't work !!

["SAX exception" IReport 3.1.2 for 3.1.1 report]

Hello,

When migrating from ireport 3.1.0 to 3.1.1 and running a 3.1.0 created report in iReport 3.1.1 I already got a "utf-8 out of sequence character" error. There are some posts about that on this forum and one guy provided a work-around that was to load the plugin "XML and schema". I did that and all is working right.

Now I am trying to migrate from 3.1.1 to 3.1.2. I get the same kind of trouble : when I edit a 3.1.1 created report, and save it without change in 3.1.2 and try to run it, I get an error :

ava.lang.Exception: 1 - org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the declaration of element 'jasperReport'.      at com.jaspersoft.ireport.jasperserver.ws.WSClient.runReport(WSClient.java:402)      at com.jaspersoft.ireport.jasperserver.ws.WSClient.runReport(WSClient.java:319)      at com.jaspersoft.ireport.jasperserver.ReportRunner.run(ReportRunner.java:70)      at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:561)      at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:986)  

It is no more "UTF8" error but it sounds like the same scenario.

Have other people got the same problem ??

Code:

java.lang.Exception:Â1Â-Âorg.xml.sax.SAXParseException:Âcvc-elt.1:ÂCannotÂfindÂtheÂdeclarationÂofÂelementÂ'jasperReport'. ÂÂÂÂatÂcom.jaspersoft.ireport.jasperserver.ws.WSClient.runReport(WSClient.java:402) ÂÂÂÂatÂcom.jaspersoft.ireport.jasperserver.ws.WSClient.runReport(WSClient.java:319) ÂÂÂÂatÂcom.jaspersoft.ireport.jasperserver.ReportRunner.run(ReportRunner.java:70) ÂÂÂÂatÂorg.openide.util.RequestProcessor$Task.run(RequestProcessor.java:561) ÂÂÂÂatÂorg.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:986) 

[JasperServer 3.0.0 Released]

In France we say "Mieux vaut tard que jamais" (=" Late is better than never")

It's for joking of course !!! Tony

[Jasperserver plug in not listing servers]

"The only thing i did was updating my system from ubuntu 8.04 to 8.10 but i dont think that this is the problem."

Logicaly, if it is really the only thing you did and if after it was not working, this should be due to this upgrade.

In the updating, has something changed on network filtering : Firewall setup? new filtering software?

On windows, I got a lot of strange things with iReport access due to the Kaspersky anti-virus.

[jasperserver 3.0 and ireport 3.1.1]

In fact, there is a thread on the iReport forum about that trouble :

jasperforge.org/plugins/espforum/view.php

and it seems there is a workaround : load the plugin "XML and Schemas"

I tested that and for me it is working.

For your information

[ERROR : Invalid byte 1 of 1-byte UTF-8 sequence]

I confirm that installing the plugin XML and Schema fixed the problem for me. Previously "corrupted" reports can now be loaded in editor.As already said, this installation forces the upgrade of the IDE environment.

In fact my error was "Invalid byte 2 of 3-byte UTF-8 sequence" and not "1 of 1-byte UTF-8 sequence" but I think that the troublr source is the same.

[User Dashboard & About Folder Structure]

hello,

I already posted something about that on this forum :

jasperforge.org/plugins/espforum/view.php

I don't know i that maps your wishes. Have a look and good luck !!

Gaby

[ERROR : Invalid byte 1 of 1-byte UTF-8 sequence]

I have posted a similar trouble on jasperserver forum and I was answered that it has been transmitted as bug.

Your work-aroundis very interesting

[JS behaviour for a user with multiple roles]

Mary,

Thanks for the links to ACEGI. I will have a look on them.

If I have a clear idea of what are the rules, I will put my understanding on this forum.

[hyperlink problem passing parameter]

I already got this trouble. In my case, it was always due to the fact that I forgot to define the corresponding input control. Even if your parameter is always transmitted by URL, you need to define an input control with the same name else your parameter wile be "null".

Hope this helps

[JS behaviour for a user with multiple roles]

Nobody has encountered this interrogation?

In my case, I have defined specific roles to which I mapped specific home pages. But if I add the role "ROLE_USER" for instance to a user which has always a specific role, then the home page becomes the "standard" repository tree of the user role.

So I think that some roles are "privilegied".

Has anybody an idea about that metaphysic question?

[jasperserver 3.0 and ireport 3.1.1]

I saw on this forum (or IReport forum) that this could be due to the version of Jasperreports. I upgraded the jar of jasperreports to 3.1.0 in the lib directory of WEB-INF in jasperserver and I always get the same error if I update a report created under IReport 3.0.0.