JasperServer Plugin Not Responding

[smclurkin]

iReport version: 2.0.0

JasperServer version: 2.0.1

iReport/JasperServer plugin version 2.0.1

 

I've copied the plugin jar to the iReport lib directory. When I startup iReport the splash screen stays on with a status of "Loading plugins".

 

Is there anything else I need to do to get the plugin to work?

 

Steve

[smclurkin]

I just upgraded to iReport 2.0.1 and I still have the same issue. I've attached a screen print of what I see. Is there a way to turn on debug while it's loading so that I could see what's causing this?

Post edited by: smclurkin, at: 2007/08/31 00:22

[smclurkin]

Couldn't upload the image, it was too large.

[harry.clarkknovalent.com]

I've just had this problem myself. I found a discussion of the server URL being hard-coded in the plugin as localhost---. Are you running Jasp Server locally? If not it might be hanging because it can't find the local server. Sounds incredible. I looked just now for the forum page, in my browser hist somewhere. I started trying to rebuild the plugin so I could fix this, but am having problems collecting everything to get it to build, haven't got around to fixing the URL, letting it be input. Maybe an expert can comment.

[harry.clarkknovalent.com]

Here's the business about the server URL, from the howto.txt file that comes with the plug-in. It was yesterday, eons ago...as noted I am trying to rebuild the plugin but haven't collected all the bits and pieces yet.

 

Another thing about Jasp Server. You are dependent on its JRE level for scriptlets. I need to import a jar for a scriptlet used in a report. iReport uses the JRE on my machine for the scriptlet compile; I have several JRE/JDKs, but it presumably uses the one that was current when iReport was installed, the current JAVA_HOME setting. Thus the scriptlet is compiled using 6.0x while Jasp Server uses 5.0x and throws incompatible class exception. Nor can you set the Java Compiler level in iReport, that I can find.

 

These cannot be new problems. Can the experts comment? Thanks.

 

4) Note on Modifying the Server Connection String

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

 

Currently, the iReport plugin has a hard-coded value used for the default URL string

that makes the connection to JasperServer. This causes a problem because the Open

Source and Pro versions of JasperServer have different URL paths ("jasperserver" vs

"ji-pro").

 

The default is:

 

http://localhost:8080/ji-pro/services/repository

 

If you are building for the Open Source JasperServer release you will need to

change "ji-pro" to "jasperserver". Like the following:

 

http://localhost:8080/jasperserver/services/repository

 

To do this you must edit the following java file and recompile:

 

<js-os-src>/jasperserver-ireport-plugin/src/main/java

 

/com/jaspersoft/jasperserver/irplugin/gui/ServerDialog.java

[harry.clarkknovalent.com]

Got the plugin to build, just had to include all the lib jars.

[harry.clarkknovalent.com]

Somehow I needed flexdoc jar as well, from

 

https://flexdock.dev.java.net/

[harry.clarkknovalent.com]

This is in the default.jasperserver_irplugin.properties in com.jaspersoft.jasperserver.irplugin package. It is referenced in ...gui.ServerDialog. This may not be the problem, but it's a start.

 

#new connection defaults

irplugin.server.url=http://localhost:8080/jasperserver/services/repository

[harry.clarkknovalent.com]

I tried changing the server URL in the properties and updating the plugin jar, but it didn't change the behavior, still hangs

[harry.clarkknovalent.com]

The plug-in hang problem can be fixed by reading the directions closely and copying *all* the plugin/lib jars to ireport/lib.

 

The compiler skew problem betw Jasper Server and iReport, which affects report scriptlets, does not seem easily fixed. The JS install doc says it isn't certified with JDK>1.5. iReport uses the Eclipse compiler, which will target different compliance levels, but there seems no way of setting that level. Can I build JS from source and get compatiblity with my scriptlet despite the non-certification? Can I build my scriptlet in Eclipse with 1.5 compliance? Hard to distribute the scriptlet to non-programmers that way. There must be some straightforward answer.

[harry.clarkknovalent.com]

The compiler iReport uses can be changed by copying a different tools.jar from the JDK/lib to ireport/lib (as I'd done to compile reports in the first place, duh). However, I also had to set the JDK version in the registry in order to use jar.exe from that JDK on a scriptlet class file to make a jar for import into JasperServer, in effect roll my machine back to JDK 1.5. This is awkward to say the least.

 

I can use the JasperServer plugin to export my report and the scriptlet jar from iReport to JS, and no longer get a class version skew exception, but it still won't run the report from JS, complains about not finding IReportScriptlet class (of which my scriptlet is a subclass). The iReport scriptlet setting is "internal support".

 

I suppose one could write a plugin to use the Eclipse compiler and pass the JDK compliance level to it for compilation. IReport will use the Eclipse if it's in the lib I gather, but I can't see how to set the compliance level. A plugin could also use jar.exe or the jar API to put the scriptlet in a jar for JasperServer.

[harry.clarkknovalent.com]

The compiler iReport uses can be changed by copying a different tools.jar from the JDK/lib to ireport/lib (as I'd done to compile reports in the first place, duh). However, I also had to set the JDK version in the registry in order to use jar.exe from that JDK on a scriptlet class file to make a jar for import into JasperServer, in effect roll my machine back to JDK 1.5. This is awkward to say the least.

 

I can use the JasperServer plugin to export my report and the scriptlet jar from iReport to JS, and no longer get a class version skew exception, but it still won't run the report from JS, complains about not finding IReportScriptlet class (of which my scriptlet is a subclass). The iReport scriptlet setting is "internal support".

 

I suppose one could write a plugin to use the Eclipse compiler and pass the JDK compliance level to it for compilation. IReport will use the Eclipse if it's in the lib I gather, but I can't see how to set the compliance level. A plugin could also use jar.exe or the jar API to put the scriptlet in a jar for JasperServer.