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]

Reply via email to