[
http://jira.amdatu.org/jira/browse/AMDATU-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivo Ladage - van Doorn resolved AMDATU-29.
------------------------------------------
Fix Version/s: 0.1.0
Resolution: Fixed
Currently there are no Guice binding issues anymore. Furthermore, as we are
replacing Shindig components by other components this issue occurs less.
> Guice in a OSGi framework
> -------------------------
>
> Key: AMDATU-29
> URL: http://jira.amdatu.org/jira/browse/AMDATU-29
> Project: Amdatu
> Issue Type: Question
> Components: Amdatu OpenSocial
> Affects Versions: 0.0.2
> Reporter: Ivo Ladage - van Doorn
> Assignee: Ivo Ladage - van Doorn
> Fix For: 0.1.0
>
>
> Apache Shindig heavily uses Guice for dependency injection. Using Guice
> modules, instances or implementation classes are bound to the Guice annotated
> constructors, fields and arguments. However, Guice modules are configured
> compile time and so does not facilitate binding services (which can be
> available or unavailable at any time) to the Guice annotated objects. An OSGi
> bridge, named Peaberry, was designed to fill this gap. It provides a way to
> bind service instances to Guice annotated objects. This however does not seem
> to work as you would like/expect. For some reason it seems that although the
> service-bound Guice objects are instantiated and published as OSGi service,
> additional static Guice objects are instantiated which are used internally by
> Shindig instead.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
