[
https://issues.apache.org/jira/browse/TAP5-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662511#action_12662511
]
Fernando commented on TAP5-443:
-------------------------------
but it's been broken on our end for a while.. since checkin: r732188
And in the exception logs, it complains about UploadModule. Are you including
that in your tests?
we include (5.1.0.0-SNAPSHOT): tapestry-core, tapestry-ioc, tapestry-spring
(5.0.18), tapestry-upload, tapestry-annotations
and even if you don't see an error, conceptually it is broken right? Two
services are declaring a @Traditional Marker.. not sure why it should work.
> 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
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
