[#TAV-217] Opening workflow fails to find XMLSpitter classes - myGrid

Details

Type: Bug
Status: Resolved
Priority: Critical
Resolution: Fixed
Affects Version/s: 1.5
Fix Version/s: 1.5
Component/s: None
Labels:
None

Description

As the title says. Classloader queried has no reference to the XMLSplitter class neither does its children or parents. Other processor may also have the same problem. Solution is to change how the classloader for loading the class is selected.

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Stuart Owen added a comment - 2006-11-03 10:38

Resolved. Converted LocalWorkers to act as 'proper' SPI with its own registry class. When loading classes by reflection from the scufl xml, it queries the LocalWorker registry for the class, which in turn queries the SPIRegistry to find the actual class.

This means that XMLSPlitters have to be added as an SPI. To prevent them being displayed in the scavenger tree they are given the category 'hidden' which are now not added to the tree view.

Show

Stuart Owen added a comment - 2006-11-03 10:38 Resolved. Converted LocalWorkers to act as 'proper' SPI with its own registry class. When loading classes by reflection from the scufl xml, it queries the LocalWorker registry for the class, which in turn queries the SPIRegistry to find the actual class. This means that XMLSPlitters have to be added as an SPI. To prevent them being displayed in the scavenger tree they are given the category 'hidden' which are now not added to the tree view.

People

Assignee:

Stuart Owen

Reporter:

Stuart Owen

Vote (0)

Watch (0)

Dates

Created:

2006-11-01 10:43

Updated:

2006-11-03 10:38

Resolved:

2006-11-03 10:38