[EMAIL PROTECTED]
>Sent: Tuesday, January 11, 2005 4:36 PM
>To: FRIESE, PETER; [EMAIL PROTECTED]
>Cc: andromda-user@lists.sourceforge.net
>Subject: RE: [Andromda-user] Spring cartridge: creating empty entities
>
>
>Hey Peter and Roy, these ideas sound good. Please file a JIRA
>
-user@lists.sourceforge.net
Subject: RE: [Andromda-user] Spring cartridge: creating empty entities
Hi Roy,
>I vote yea for A, B, and C. I have already found myself implementing
>these methods by hand and have been too lazy to say or do
>anything about
>it. ;-)
I'm glad I'm not the
ehalf Of
[EMAIL PROTECTED]
Sent: Tuesday, January 11, 2005 8:51 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: andromda-user@lists.sourceforge.net
Subject: RE: [Andromda-user] Spring cartridge: creating empty entities
Ok, I will do so.
BTW: how are plans regarding the remoting capabilities of Spri
Hi Roy,
>I vote yea for A, B, and C. I have already found myself implementing
>these methods by hand and have been too lazy to say or do
>anything about
>it. ;-)
I'm glad I'm not the only one having ideas like this :-)
>I am not sure I understand D, if you already have a factory method on
>the
Hi Peter,
On Tue, 2005-01-11 at 12:05 +0100, [EMAIL PROTECTED] wrote:
> We've got the following suggestions:
> a) add a factory method "public static create" for each entity,
> returning a "new EntityImpl()"
> b) add this factory method to the DAO
> c) introduce one global factory, containing c
Hi,
we are using the Spring cartridge on a project - great work so far!
The GUI we're building is an Eclipse Rich Client and we're currently
elaborating some GUI concepts. One of our ideas is to create GUI helper classes
that facilitate handling entities in the GUI. Let me give you an example:
