[
https://issues.apache.org/jira/browse/TAPESTRY-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493717
]
Howard M. Lewis Ship commented on TAPESTRY-1425:
------------------------------------------------
Looks like we should chnage the Alias service's object provider to NO-OP until
the mode is set (rather than fail). I'm a little nervous about injections that
require the Alias service to properly disambiguate the injection.
> 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]