[jira] Updated: (TAPESTRY-2267) Services that are dependencies of other EagerLoad services may not be eagerly loaded

["Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>]

     [ https://issues.apache.org/jira/browse/TAPESTRY-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAPESTRY-2267:
-------------------------------------------

    Component/s: tapestry-ioc
        Summary: Services that are dependencies of other EagerLoad services may not be eagerly loaded  (was: Eagerload sometimes 'fails' when multiple modules are used )

> Services that are dependencies of other EagerLoad services may not be eagerly loaded
> ------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-2267
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2267
>             Project: Tapestry
>          Issue Type: Bug
>          Components: tapestry-ioc
>    Affects Versions: 5.0.11
>            Reporter: Martijn Brinkers
>            Assignee: Howard M. Lewis Ship
>         Attachments: TapestryIOCEagerLoadTest.tar.gz
>
>
> I have two modules, module A and module B. Module A has two services SA1 and SA2 both of them are eager loaded. Module B depends on module A so a SubModule annotation is added to Module B. Module B has one service SB1. SB1 is also eager loaded. SB1 needs SA1 for building the service. 
> If the registry is started and the services are eager loaded using performRegistryStartup() only SB1 and SA2 are eager loaded. SA1 is build when used whereas I would expect it to be eager loaded as well. 
>  

-- 
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org