[
https://issues.apache.org/jira/browse/FELIX-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919249#action_12919249
]
Bengt Rodehav commented on FELIX-2636:
--------------------------------------
Thanks a lot Clement.
Yes, you'r right, the FILE INSTALL vs BUNDLE CACHE question is better suited
for the mailing list since it's not really connected to this issue (not
connected to iPOJO at all probably).
Looking forward to the release.
> Cannot control the validity of an iPOJO instance using a configuration
> property
> -------------------------------------------------------------------------------
>
> Key: FELIX-2636
> URL: https://issues.apache.org/jira/browse/FELIX-2636
> Project: Felix
> Issue Type: Bug
> Components: iPOJO
> Affects Versions: iPOJO-1.4.0
> Reporter: Bengt Rodehav
> Assignee: Clement Escoffier
> Fix For: iPOJO-1.8.0
>
>
> Controlling the validity of an iPOJO instance as follows doesn't work:
> @Controller
> @Property(name = "connect.enabled", mandatory = true)
> private boolean mValid = false;
> When initialising mValid to false (as above), the iPOJO instance becomes
> invalid even though the configuration property (connect.enabled in this case)
> is true.
> On the other hand, if the following code is used...
> @Controller
> @Property(name = "connect.enabled", mandatory = true)
> private boolean mValid = true;
> ...then the instance becomes valid even though the configuration property is
> false.
> I use Karaf 1.6.0 with file installer 3.0.2 in the scenario above. The
> problem only occurs when starting Karaf. Subsequent changes of the
> configuration property will change the validity of the instance correctly.
> The problem does not show when using iPOJO 1.6.0 but it's still important to
> make sure that the above described scenario is supported by iPOJO.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
