[
https://issues.apache.org/jira/browse/TAP5-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade updated TAP5-1029:
---------------------------------
Labels: bulk-close-candidate (was: )
This issue has been last updated about 1.5 years ago, has no assignee, affects
an old version of Tapestry that is not actively developed anymore, and is
therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry (5.4-beta-6, which is available from Maven Central), please update it
as soon as possible. In the case of a feature request, please discuss it with
the Tapestry developer community on the [email protected] mailing list
first.
> Provide public API for injecting the dependencies into already-constructed
> instances.
> -------------------------------------------------------------------------------------
>
> Key: TAP5-1029
> URL: https://issues.apache.org/jira/browse/TAP5-1029
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-ioc
> Affects Versions: 5.2
> Reporter: Igor Drobiazko
> Labels: bulk-close-candidate
>
> To improve the acceptance of tapestry-ioc as IoC container of non-Tapestry
> applications we should provide a public API for injecting dependencies into
> already-constructed instances. In most non-Tapestry applications autobuilding
> is not appropriate if you want to inject dependencies. For example an
> Activator of an OSGi bundle is created by the OSGI environment. There are
> even more use cases.
> Maybe we should provide a new service called 'Injector' that whould use
> InternalUtils.injectIntoFields and InternalUtils.invokePostInjectionMethods.
> This service could be reused in Registry.autibuild.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
