[
https://issues.apache.org/jira/browse/TAP5-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fernando reopened TAP5-443:
---------------------------
But the thing is that just reading the markers. Some code is asking for
@Traditional, and TWO services are marked with that.. so it can't figure it
out...
and someone on the mailing list is having the same issues!
are you sure the unit test actually brings in all of the tapestry dependencies
while testing? Maybe this should be an integration test, not a unit test??
> There are two services that implement ComponentEventResultProcessor, and
> declare the @Traditional marker
> --------------------------------------------------------------------------------------------------------
>
> Key: TAP5-443
> URL: https://issues.apache.org/jira/browse/TAP5-443
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.1.0.0
> Reporter: Fernando
> Assignee: Howard M. Lewis Ship
> Priority: Blocker
>
> This causes a bad exception when tapestry tries to resolve an IoC dependency
> asking for @Traditional ComponentEventResultProcessor...
> I think you just want to remove it from
> ComponentInstanceResultProcessor.java, and remove it from
> TapestryModule.java:1346 (where it uses the secondary marker,
> @ComponentInstanceProcessor ).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
