You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2012/08/18 01:54:37 UTC

[jira] [Commented] (TAP5-1823) Construction of service 'ServiceOverride' has failed due to recursion

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

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

The supplied patch uses service decoration to disable the service.

https://github.com/apache/tapestry5/pull/3

That does not work, as the service has @PreventServiceDecoration applied.
                
> Construction of service 'ServiceOverride' has failed due to recursion
> ---------------------------------------------------------------------
>
>                 Key: TAP5-1823
>                 URL: https://issues.apache.org/jira/browse/TAP5-1823
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3.1
>            Reporter: Alexander Gavrilov
>            Assignee: Howard M. Lewis Ship
>            Priority: Blocker
>
> After switching to the 5.3 version my simple project stop launching failing with exception: java.lang.IllegalStateException: Construction of service 'ServiceOverride' has failed due to recursion: the service depends on itself in some way. Please check org.apache.tapestry5.ioc.internal.services.ServiceOverrideImpl(Map) (at ServiceOverrideImpl.java:31) via org.apache.tapestry5.ioc.services.TapestryIOCModule.bind(ServiceBinder) (at TapestryIOCModule.java:49) for references to another service that is itself dependent on service 'ServiceOverride'.
> It's seems that the problem is with TapestryModule#productionModeOverrides. This method contributes to the ServiceOverride and requires SymbolConstants.PRODUCTION_MODE. This dependency requires to realize all SymbolProvider services and if there is any contribution to one of ApplicationDefaults or FactoryDefaults that requires some external service application fails with  circular dependency error.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira