Oscar,
You've convinced me... we should keep our entities consistent across the
layers. More discussion inline below
Dan
On 5 August 2013 17:00, GESCONSULTOR - Óscar Bou o@gesconsultor.comwrote:
But I presume there was a reason that you put your call to
Thanks for raising this Oscar, I've never really understood why the viewers
are responsible for validation but never took the time to dive into it.
Cheers,
Jeroen
On Tue, Aug 6, 2013 at 8:15 AM, Dan Haywood
d...@haywood-associates.co.ukwrote:
Oscar,
You've convinced me... we should keep
Dan Haywood created ISIS-488:
Summary: Derive Isis' MandatoryFacet from JDO @Column(allowNulls=)
annotation
Key: ISIS-488
URL: https://issues.apache.org/jira/browse/ISIS-488
Project: Isis
Issue
Thanks for your responses, Dan and Jeroen. Nice to be in such a responsive
environment :-)
Part of the reason is in keeping the responsibilities of the various
implementations consistent with each other. The Wicket viewer and the RO
viewer now both set up transactions before doing any work,
For the last part of the email (property validation) I was just looking again
at the JSR-349 specification, whose last version has just been approved and
incorporated to Java 7.
Seems that the reference implementation (Hibernate Validator) is Apache
licensed [1].
How should it be used within
[
https://issues.apache.org/jira/browse/ISIS-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-488:
-
Summary: Derive Isis' MandatoryFacet from JDO @Column(allowNulls=)
annotation, and provide @Mandatory
[
https://issues.apache.org/jira/browse/ISIS-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-488:
-
Description:
Thus:
@javax.jdo.annotations.Column(allowNulls=false)
public String getFoo() { ... }
is
[
https://issues.apache.org/jira/browse/ISIS-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731631#comment-13731631
]
ASF subversion and git services commented on ISIS-488:
--
Commit
Folks,
For those working off snapshots, just wanted to flag a change I've just
committed, ISIS-488 [1], that may break your code (assuming you are using
the JDO objectstore).
Currently, to specify that a property is not required in Isis, we use
@Optional. If not present, then the property is
