Error while switching to the Processing tab

[mordenkainen]

When I switch to the processing tab, I get following message:

ReferenceError: "ImportPackage" is not defined in <eval> at line number 2

.

What I expect: anything that goes smooth

What I get: an error message and after that scirpt window is opened.

I'm totally new to the Wandora, and I'm still studying it. So I'm not sure how it should work instead of giving error

[akivela]

Hi Mordenkainen

The Processing tab is used to program and run Processing scripts. Wandora compiles the Processing script into Java bytecode. If the Processing script is not valid Java code, the compilation fails and Wandora views an error message. I assume you have accidentally or by mistake entered something into the processing script that breaks it. I assume your Processing script is somehow broken. Also, we haven't tested the Processing tab with Java 8 yet. I recall it has some problems with Java 8.

You can load working/tested script by clicking the Open button > Open sketch from file.... Select 'TopicRing.sketch' and Run the script. If running fails, please send the error message.

Check the documentation of Wandora's Processing tab at
http://wandora.org/wiki/Processing_topic_panel

Also, information about Processing itself can be found at
https://www.processing.org

Kind regards,
Aki / Wandora Team

[mordenkainen]

Hi Akivela. Thank you for fast reply.

I had no chance to enter any processing code. The error shows when I click on the Processing Pane and before any edition was added to it. Probably some code is trying to run at the creation of the panel.

And you had guessed right, I'm running wandora on the 8th version of oracle jvm. I have also 6th and 7th versions installed, so it would not be difficult to switch to them.

[akivela]

Hi Mordenkainen. Great, just change the default Java version to 7 and you should be able to use Wandora's Processing tab.

It looks like the official version number of Processing is 2 these days. Unfortunately we haven't updated Wandora's Processing engine (yet) and Wandora supports only Processing version 1.5. There may be some changes in the Processing api between versions 1.5 and 2. This may become an issue if you decide to program Processing scripts/sketches by your self and follow the documentation at the Processing web site (https://www.processing.org/).

Kind regards,
Aki / Wandora Team

[mordenkainen]

I have tried to run wandora under 7 version of the jvm. It showed me two similar errors about missing script engine:

Code: Select all

SEVERE: Error reading options file
java.lang.RuntimeException: Couldn't find a suitable script engine
   at org.wandora.query2.QueryRunner.<init>(QueryRunner.java:65)
   at org.wandora.query2.QueryRunner.<init>(QueryRunner.java:73)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
   at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
   at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
   at java.lang.Class.newInstance(Class.java:379)
   at org.wandora.modules.ModuleManager.parseXMLParamElement(ModuleManager.java:867)
   at org.wandora.modules.ModuleManager.parseXMLOptionsElement(ModuleManager.java:925)
   at org.wandora.modules.ModuleManager.parseXMLModuleElement(ModuleManager.java:1006)
   at org.wandora.modules.ModuleManager.parseXMLConfigElement(ModuleManager.java:1120)
   at org.wandora.modules.ScopedModuleManager.parseXMLConfigElement(ScopedModuleManager.java:201)
   at org.wandora.application.modulesserver.ModuleBundle.parseXMLConfigElement(ModuleBundle.java:71)
   at org.wandora.modules.ModuleManager.readXMLOptionsFile(ModuleManager.java:1158)
   at org.wandora.application.modulesserver.WandoraModuleManager.readBundle(WandoraModuleManager.java:58)
   at org.wandora.application.modulesserver.WandoraModuleManager.readBundleDirectories(WandoraModuleManager.java:122)
   at org.wandora.application.modulesserver.WandoraModuleManager.readBundleDirectories(WandoraModuleManager.java:128)
   at org.wandora.application.modulesserver.WandoraModuleManager.readBundles(WandoraModuleManager.java:114)
   at org.wandora.application.modulesserver.WandoraModulesServer.readBundleDirectories(WandoraModulesServer.java:125)
   at org.wandora.application.modulesserver.WandoraModulesServer.<init>(WandoraModulesServer.java:95)
   at org.wandora.application.Wandora.getHTTPServer(Wandora.java:298)
   at org.wandora.application.WandoraMenuManager.refreshServerMenu(WandoraMenuManager.java:348)
   at org.wandora.application.WandoraMenuManager.refreshMenus(WandoraMenuManager.java:179)
   at org.wandora.application.WandoraMenuManager.<init>(WandoraMenuManager.java:144)
   at org.wandora.application.Wandora.initializeWandora(Wandora.java:546)
   at org.wandora.application.Wandora.<init>(Wandora.java:286)
   at org.wandora.application.Wandora.main(Wandora.java:2288)


[akivela]

Wandora uses Mozilla Rhino javascript engine for quering (http://www.wandora.org/wiki/Query_language). Wandora contains two server modules that demonstrate how quering is used with embedded HTTP server. It looks like the embedded HTTP server fails to start because these two services throw exception. Mozilla Rhino is not found. A quick fix is to remove failing services by deleting folders

build/resources/server/querydemo
build/resources/server/queryconsole

However, I suggest you first try to reinstall Java SDK version 7. Wandora uses Mozilla Rhino as a part of Search too.

Kind Regards,
Aki / Grip

[mordenkainen]

Probably my icedtea jvm misses rhino engine. It may be installed separately, I suppose

[akivela]

Of course, Wandora shouldn't fail if some server modules fail. Github (https://github.com/wandora-team/wandora) contains some enhancements for the application robustness. These enhancements will be part of next Wandora release.

I am rather confident that these changes doesn't resolve all problems caused by the Java version 8.