tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TAP5-443) There are two services that implement ComponentEventResultProcessor, and declare the @Traditional marker
Date Thu, 15 Jan 2009 17:32:59 GMT

    [ https://issues.apache.org/jira/browse/TAP5-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664185#action_12664185
] 

Howard M. Lewis Ship commented on TAP5-443:
-------------------------------------------

What was really needed was a @Primary annotation to distinguish the pipeline from the services
contributed into the pipeline.

> 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.


Mime
View raw message