Re: GSOC2013 - ISIS-371 (an android viewer)

Hi Dan, Thank you for the information. I started developing actual application instead that dummy one I created. Before that I needed a plan to figure out correct paths to develop this. So I created a document mentioning abstract overview of the app [1] I'm going to develop, Please refer to that do

[jira] [Updated] (ISIS-386) Provide the ability to force a reload of an object by the JDO objectstore.

[ https://issues.apache.org/jira/browse/ISIS-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-386: - Description: This is needed because, it would seem, DataNucleus does not maintain 1:m bidirectional relati

[jira] [Resolved] (ISIS-386) Provide the ability to force a reload of an object by the JDO objectstore.

[ https://issues.apache.org/jira/browse/ISIS-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood resolved ISIS-386. -- Resolution: Fixed > Provide the ability to force a reload of an object by the JDO objectstore. >

[jira] [Created] (ISIS-386) Provide the ability to force a reload of an object by the JDO objectstore.

Jeroen van der Wal created ISIS-386: --- Summary: Provide the ability to force a reload of an object by the JDO objectstore. Key: ISIS-386 URL: https://issues.apache.org/jira/browse/ISIS-386 Project: I

Re: A heavier or smaller root aggregate

So, one last mail in this thread. I've not cc'ed Vaughn this time, so we won't get a reply (and I don't think he would want to anyway), but anyway... The point that Vaughn makes about "allowing your consistency boundaries to change per use case" is interesting. And I remember Udi Dahan make this

Re: A heavier or smaller root aggregate

Your bias may be mostly due to not actually using the Aggregate pattern. If you were truly using Aggregates to define transactional consistency boundaries then reference by id would not be a problem. (Maybe you allow your consistency boundaries to change per use case.) You don't have to use Aggrega

Re: A heavier or smaller root aggregate

Thanks for commenting on this, Vaughn. You are right it is the consensus view, because the consensus seems for some reason to focus on NoSQL and non-transactional databases. I remain confused by this; the vast majority of enterprise systems are built against RDBMS, and that will the case. I stil

Re: INTRODUCTION

And a couple more interesting links, which suggest that adding a UML-like browser of the Isis DSL should be quite easy.. [8] http://vimeo.com/35256324 - Generic Graph Viev: Discovery Demo [9] http://vimeo.com/35263430 - Multitouch Gestures in the Generic Graph View [10] http://vimeo.com/25551186

Re: A heavier or smaller root aggregate

Note the specific word "prefer" at the outset of the advice. This advice reflects the current consensus view among DDD leaders, but there are reasons to break the rule(s) of thumb (RoT meaning, do this by default but maybe not always). Also note the following this specific rule in question could a

Re: INTRODUCTION

On 18 April 2013 08:58, Sabhya Kaushal wrote: > > But in the meantime, i have made some progress, thought you would like to > know: > > 1. designed two domain specific languages using XText technology. Though > not that full fledged, sophisticated and complex, but they definitely are > in a worki