[
https://issues.apache.org/jira/browse/TAPESTRY-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493844
]
Ben Sommerville commented on TAPESTRY-1425:
-------------------------------------------
Thats a good solution.
My use case didn't need the alias service at all, the services were all
unambiguous. It was just that the aliases were checked first & failed hard.
> Eager Loaded service (builder) cannot use object injection
> ----------------------------------------------------------
>
> Key: TAPESTRY-1425
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1425
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.4
> Reporter: Ben Sommerville
> Priority: Minor
>
> A service which is EagerLoaded cannot use object injection, it must use
> InjectService.
> If the eager loaded service uses object injection then it will cause an error
> because the alias service has not had its mode set when eager loaded services
> are created.
> e..g This builder method results in an error
> @EagerLoad
> public RegistryShutdownListener buildFileCleanerCleanup( RegistryShutdownHub
> hub)
> When service injection is used it is ok.
> @EagerLoad
> public RegistryShutdownListener
> buildFileCleanerCleanup(@InjectService("RegistryShutdownHub")
> RegistryShutdownHub hub)
> Not sure if this can actually be fixed, or if it just needs to be documented.
--
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]
