Turbine 2.3.2 compatible Service to use YAAFI instead of the AvalonComponentService

• Key: TRB-27
• Type: Improvement
• Status: Closed
• Resolution: Fixed
• Priority: Major
• Assignee: Scott Eade
• Reporter: Thomas Vandahl
• Component/s: Fulcrum
• Affects Version/s: Core 2.3.2
• Fix Version/s: Core 2.3.3

Description

I changed a few lines in the TurbineYaafiComponentService to make it run as a Drop-In replacement of the TurbineAvalonComponentService which is based on ECM. To use this, you just need to change the line

services.AvalonComponentService.classname=org.apache.turbine.services.avalon.TurbineAvalonComponentService

into

services.AvalonComponentService.classname=org.apache.turbine.services.yaafi.TurbineYaafiComponentService

and add

services.AvalonComponentService.containerConfiguration = /WEB-INF/conf/containerConfiguration.xml

to the TurbineResources.properties file.

Comments

[Thomas Vandahl]

Just the source for there is no source package for this.

[Siegfried Goeschl]

Since we have discussed the topic early just a quick comment - using the Component interface is deprecated (see http://wiki.apache.org/avalon/ContainerStory and the chapter "How Components Became Services") - in the long run we have to switch back to returning Object instead of Component (as it was done in the original implementation)

[Jürgen Hoffmann]

So what do we return instead of Components then? TurbineServices? Aren't we doing so at the current Stage? ServiceManager.getService(ServiceName) looks a bit Different than ComponentManager.lookup(ComponentName) but if it returns Object is essentially the same, isn't it?

[Thomas Vandahl]

This is for Turbine 2.3.2, remember. There, the method AvalonComponentService.lookup returns Component. If I return Object in this case, this would break code which relies on the Component interface. I agree that for Turbine 2.4 this is not an issue, but for 2.3 it is relevant.

[Scott Eade]

org.apache.turbine.services.avaloncomponent.ACSYaafiComponentService has been committed to the 2.3 branch along with docs and a basic test case.

[Thomas Vandahl]

Fix is in 2.3.3-release