[
https://issues.apache.org/jira/browse/TAPESTRY-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-2267.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.12
Changed the logic to collect all eager load proxies from all modules before
eagerly loading any of them. It used to be per-module which could lead to the
unexpected results.
> 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
> Fix For: 5.0.12
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
