[
https://issues.apache.org/jira/browse/FELIX-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587670#action_12587670
]
clement.escoffier edited comment on FELIX-533 at 4/10/08 8:16 AM:
------------------------------------------------------------------
I add this feature (committed in the revision #646835), and update the
documentation (http://felix.apache.org/site/service-requirement-handler.html).
So, to disable the Nullable object injection just add the 'nullable="false"'
attribute in your service requirement description. So, iPOJO will inject null
instead of a Nullable object when no providers are available.
Be aware that, the Nullable system is enable by default.
was (Author: clement.escoffier):
I add this feature, and update the documentation
(http://felix.apache.org/site/service-requirement-handler.html).
So, to disable the Nullable object injection just add the 'nullable="false"'
attribute in your service requirement description. So, iPOJO will inject null
instead of a Nullable object when no providers are available.
Be aware that, the Nullable system is enable by default.
> Deactivate the Nullable objects
> -------------------------------
>
> Key: FELIX-533
> URL: https://issues.apache.org/jira/browse/FELIX-533
> Project: Felix
> Issue Type: Improvement
> Components: iPOJO
> Reporter: Guillaume Sauthier
>
> Sometimes, it can be useful to not always have a Nullable object injected
> even when the dependency is not available.
> Sometimes, the service user simply wants to really test himself if the
> dependency has been injected or not.
> I think that an option to disable nullable creation will be really useful
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
