Modifying similarly named properties of different roles does not work
---------------------------------------------------------------------
Key: QI-273
URL: http://issues.ops4j.org/browse/QI-273
Project: Qi4j
Issue Type: Bug
Components: Core Runtime
Affects Versions: 1.2
Environment: Qi4j.
Reporter: Stanislav Muhametsin
Assignee: Rickard Öberg
Fix For: 1.3
Attachments: entity_state_test.zip
If one has two similarly named properties, but in different role interfaces,
setting their values via prototype does not work. The test case is included.
This is most likely because in JSONEntityState stateName.name() is used instead
of stateName.toString(). Also, since JSONEntityState stores identity separately
from other properties, it is possible to change it via builder's
instanceFor(...) method, but not inside, let's say, Lifecycle's mixin.
There is discussion about changing identity in Lifecycle, but if it is not
desired behaviour in any situation, the exception should be thrown if lifecycle
tries to modify identity. Now it completes normally, but does not actually
change the identity.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
