Tapestry
  1. Tapestry
  2. TAPESTRY-2267

Services that are dependencies of other EagerLoad services may not be eagerly loaded

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.11
    • Fix Version/s: 5.0.12
    • Component/s: tapestry-ioc
    • Labels:
      None

      Description

      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.

        Activity

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Martijn Brinkers
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development