[jira] [Updated] (ISIS-404) Testing if a wrapped Domain Object has been persisted fails
[ https://issues.apache.org/jira/browse/ISIS-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen van der Wal updated ISIS-404: Assignee: Dan Haywood (was: Jeroen van der Wal) Testing if a wrapped Domain Object has been persisted fails - Key: ISIS-404 URL: https://issues.apache.org/jira/browse/ISIS-404 Project: Isis Issue Type: Bug Components: Core Affects Versions: core-1.1.0 Environment: Testing against current JUnit viewer snapshot over the 1.0.2 quickstart prototype. Reporter: Oscar Bou Assignee: Dan Haywood Labels: test Fix For: core-1.7.0 While doing tests over factory actions, one assert would be to verify the object has been persisted through the DomainObjectContainer.isPersistent(domainObject) method. If the evaluation is done over a wrapped object, it returns false. If it's done over the original object, it returns true. As an example: // Test if the Domain Object has been persisted. assertTrue(domainObjectContainer .isPersistent(communicationPathAssociatedWithNode)); // Node must be wrapped for the Apache Isis validators to be executed. communicationPathAssociatedWithNode = wrapped(communicationPathAssociatedWithNode); assertTrue(domainObjectContainer .isPersistent(communicationPathAssociatedWithNode)); The last assertion fails. The only difference I expected was the validation of the programming model. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-404) Testing if a wrapped Domain Object has been persisted fails
[ https://issues.apache.org/jira/browse/ISIS-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-404: - Fix Version/s: (was: core-1.4.0) core-1.5.0 Testing if a wrapped Domain Object has been persisted fails - Key: ISIS-404 URL: https://issues.apache.org/jira/browse/ISIS-404 Project: Isis Issue Type: Bug Components: Core Affects Versions: core-1.1.0 Environment: Testing against current JUnit viewer snapshot over the 1.0.2 quickstart prototype. Reporter: Oscar Bou Assignee: Oscar Bou Labels: test Fix For: core-1.5.0 While doing tests over factory actions, one assert would be to verify the object has been persisted through the DomainObjectContainer.isPersistent(domainObject) method. If the evaluation is done over a wrapped object, it returns false. If it's done over the original object, it returns true. As an example: // Test if the Domain Object has been persisted. assertTrue(domainObjectContainer .isPersistent(communicationPathAssociatedWithNode)); // Node must be wrapped for the Apache Isis validators to be executed. communicationPathAssociatedWithNode = wrapped(communicationPathAssociatedWithNode); assertTrue(domainObjectContainer .isPersistent(communicationPathAssociatedWithNode)); The last assertion fails. The only difference I expected was the validation of the programming model. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (ISIS-404) Testing if a wrapped Domain Object has been persisted fails
[ https://issues.apache.org/jira/browse/ISIS-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-404: - Fix Version/s: (was: core-1.3.0) core-1.4.0 Assignee: Oscar Bou (was: Dan Haywood) Testing if a wrapped Domain Object has been persisted fails - Key: ISIS-404 URL: https://issues.apache.org/jira/browse/ISIS-404 Project: Isis Issue Type: Bug Components: Core Affects Versions: core-1.1.0 Environment: Testing against current JUnit viewer snapshot over the 1.0.2 quickstart prototype. Reporter: Oscar Bou Assignee: Oscar Bou Labels: test Fix For: core-1.4.0 While doing tests over factory actions, one assert would be to verify the object has been persisted through the DomainObjectContainer.isPersistent(domainObject) method. If the evaluation is done over a wrapped object, it returns false. If it's done over the original object, it returns true. As an example: // Test if the Domain Object has been persisted. assertTrue(domainObjectContainer .isPersistent(communicationPathAssociatedWithNode)); // Node must be wrapped for the Apache Isis validators to be executed. communicationPathAssociatedWithNode = wrapped(communicationPathAssociatedWithNode); assertTrue(domainObjectContainer .isPersistent(communicationPathAssociatedWithNode)); The last assertion fails. The only difference I expected was the validation of the programming model. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ISIS-404) Testing if a wrapped Domain Object has been persisted fails
[ https://issues.apache.org/jira/browse/ISIS-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-404: - Fix Version/s: core-1.3.0 Affects Version/s: core-1.1.0 Testing if a wrapped Domain Object has been persisted fails - Key: ISIS-404 URL: https://issues.apache.org/jira/browse/ISIS-404 Project: Isis Issue Type: Bug Components: Core Affects Versions: core-1.1.0 Environment: Testing against current JUnit viewer snapshot over the 1.0.2 quickstart prototype. Reporter: Oscar Bou Assignee: Dan Haywood Labels: test Fix For: core-1.3.0 While doing tests over factory actions, one assert would be to verify the object has been persisted through the DomainObjectContainer.isPersistent(domainObject) method. If the evaluation is done over a wrapped object, it returns false. If it's done over the original object, it returns true. As an example: // Test if the Domain Object has been persisted. assertTrue(domainObjectContainer .isPersistent(communicationPathAssociatedWithNode)); // Node must be wrapped for the Apache Isis validators to be executed. communicationPathAssociatedWithNode = wrapped(communicationPathAssociatedWithNode); assertTrue(domainObjectContainer .isPersistent(communicationPathAssociatedWithNode)); The last assertion fails. The only difference I expected was the validation of the programming model. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
