myGrid

BSF scripting host has maven dependency problems

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Won't Fix
  • Affects Version/s: 1.5
  • Fix Version/s: 1.5.2
  • Component/s: Taverna GUI
  • Labels:
    None

Description

When adding a BSF Scripting host (Not the beanshell), and clicking "Configure", nothing happens, in the console a stack trace appears:

Exception in thread "AWT-EventQueue-0" java.lang.NoClassDefFoundError: org/apache/bsf/debug/BSFDebugManager
        at net.sourceforge.taverna.scuflworkers.bsf.BSFConfigPanel.<init>(BSFConfigPanel.java:340)
        at net.sourceforge.taverna.scuflworkers.bsf.BSFEditor$1.actionPerformed(BSFEditor.java:29)
        at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1882)
        at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2202)
        at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
        at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
        at javax.swing.AbstractButton.doClick(AbstractButton.java:334)
        at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1000)
        at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1041)
        at java.awt.Component.processMouseEvent(Component.java:5554)
        at javax.swing.JComponent.processMouseEvent(JComponent.java:3126)
        at java.awt.Component.processEvent(Component.java:5319)
        at java.awt.Container.processEvent(Container.java:2010)
        at java.awt.Component.dispatchEventImpl(Component.java:4021)
        at java.awt.Container.dispatchEventImpl(Container.java:2068)
        at java.awt.Component.dispatchEvent(Component.java:3869)
        at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4256)
        at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3936)
        at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3866)
        at java.awt.Container.dispatchEventImpl(Container.java:2054)
        at java.awt.Window.dispatchEventImpl(Window.java:1774)
        at java.awt.Component.dispatchEvent(Component.java:3869)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
        at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:269)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:184)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:176)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)

Sounds like a dependency problem.

In fact, dependencies on jython, jacl, jsfperl etc. are not used by the bsf artifact, as it is taverna-contrib declaring those dependencies, and not bsf.

So the BSF processor don't work at all until we redefine those dependencies.

Issue Links

Activity

Hide
June Finch added a comment - 2007-02-16 10:50

Stuart - does anyone use this/have reported it from the community itself? Thanks. June.

Show
June Finch added a comment - 2007-02-16 10:50 Stuart - does anyone use this/have reported it from the community itself? Thanks. June.
Hide
Stuart Owen added a comment - 2007-02-16 11:12

The bug described here is now fixed. But the processor itself doesn't seem to work as it can find classes required to run the different language types.

This was raised by a user, but this processor is rarely used as the Beanshell processor is preferred.
This processor is experimental code contributed some time in the past (its part of the contrib package) and was hidden. It somehow reappeared during
the 1.4.x release.
Since at the moment it doesn't work and we haven't had any (bar 1) complaints it can probably be removed, and point users to the Beanshell processor if they ask where its gone.

Show
Stuart Owen added a comment - 2007-02-16 11:12 The bug described here is now fixed. But the processor itself doesn't seem to work as it can find classes required to run the different language types. This was raised by a user, but this processor is rarely used as the Beanshell processor is preferred. This processor is experimental code contributed some time in the past (its part of the contrib package) and was hidden. It somehow reappeared during the 1.4.x release. Since at the moment it doesn't work and we haven't had any (bar 1) complaints it can probably be removed, and point users to the Beanshell processor if they ask where its gone.
Hide
Stuart Owen added a comment - 2007-04-27 16:23

Remove the processor, it doesn't and has never worked and is not maintained by us.

Show
Stuart Owen added a comment - 2007-04-27 16:23 Remove the processor, it doesn't and has never worked and is not maintained by us.
Hide
Stuart Owen added a comment - 2007-05-08 16:28

The SPI declaration of the Scavenger has been removed, disabaling the ability to use this processor in a new workflow. The code and the SPI for the ProcessorInfoBean remains in place to allow any workflows that currently contain the BSF processor to continue to run.

Show
Stuart Owen added a comment - 2007-05-08 16:28 The SPI declaration of the Scavenger has been removed, disabaling the ability to use this processor in a new workflow. The code and the SPI for the ProcessorInfoBean remains in place to allow any workflows that currently contain the BSF processor to continue to run.

People

Vote (0)
Watch (0)

Dates

  • Created:
    2006-12-23 22:49
    Updated:
    2007-05-08 16:28
    Resolved:
    2007-05-08 16:28