[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[jira] [Commented] (ARIES-1805) Blueprint core does not honor Java beans specification

    [ ] 

Guillaume Nodet commented on ARIES-1805:

Committing to ...
	M	blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/utils/
	M	blueprint/blueprint-core/src/test/java/org/apache/aries/blueprint/utils/
Committed r1832658

Thx for the test, I've added another one to make sure the method declaration order did not affect the result.

> Blueprint core does not honor Java beans specification
> ------------------------------------------------------
>                 Key: ARIES-1805
>                 URL:
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>    Affects Versions: blueprint-core-1.8.0
>            Reporter: Andrea Tarocchi
>            Assignee: Guillaume Nodet
>            Priority: Major
> Aries blueprint core, to consider a property legit, checks that is and get access methods are not present at the same time: specifically:
> looking at java bean specification:
> it seems that both access methods ({{is}} and {{get}}) are allowed to be present at the same time, in that case, the {{is}} has to be used:
> bq. *8.3.2* Boolean properties In addition, for boolean properties, we allow a getter method to match the pattern: public boolean is<PropertyName>(); This “is<PropertyName>” method may be provided instead of a “get<PropertyName>” method, or it may be provided in addition to a “get<PropertyName>” method. In either case, if the “is<PropertyName>” method is present for a boolean property then we will use the “is<PropertyName>” method to read the property value.
> Should the Aries implementation be modified accordingly?
> I've provided a test case in this PR
> If possible,  would be nice to have this available to version {{1.8.0}} as well.

This message was sent by Atlassian JIRA