[TAPESTRY-2647] IOC services bound using a marker behave differently than services with a serviceId thus producing a StackOverflow

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 5.0.14
• Component/s: tapestry-ioc
• Assignee: Howard Lewis Ship
• Reporter: Kristian Marinkovic
• Created: 07/Sep/08 21:31
• Updated: 09/Sep/08 21:55
• Resolved: 09/Sep/08 21:53

Description

the module class below produces a StackOverflow if i try to call the chain. if i use a serviceId instead of the marker annotation everything work as expected. it seems, that a marker annotation does not have the same behaviour as a serviceId. see also the attached maven project that examplifies the problem.

public final class StackOverflowModule
{
public static void bind(ServiceBinder binder)

{ binder.bind(ChainInterface.class, HelloWorld.class).withMarker(Default.class); }

public ChainInterface buildChainInterface(List<ChainInterface> chainItems, ChainBuilder builder)

{ return builder.build(ChainInterface.class, chainItems); }

public void contributeChainInterface(OrderedConfiguration<ChainInterface> chainItems,
@Default ChainInterface helloWorld)

{ chainItems.add("Default", helloWorld); }

}

Issue Links

• is related to: TAPESTRY-2655 Services defined with the bind() method may conflict with services from service builder methods without error