mdarad-toolbox-devs

[Mdarad-toolbox-devs] Save or not to save the children...

[Philippe B. <phi...@el...>]

Hi!
When a composition exists between two entities, the interface generated 
enables saving the child object.  When the child object is saved, the 
parent is automatically saved.

Shouldn't we have the child object saved only when the parent is saved 
(in the interface) ??
What do you think ?

Philippe

Re: [Mdarad-toolbox-devs] Save or not to save the children...

[<fra...@po...>]

Hi,

I agree.  That is the main reason why we brought in the context stack=
 if=20
I remember correctly.  To make the interface more intuitive we would=
=20
need to change the link name in the children edition form from 'save'=
 to=20
'add' to make it obvious that we are adding and not saving the entity=
.

Fran=E7ois

Philippe Brouillette wrote:

> Hi!
> When a composition exists between two entities, the interface=20
> generated enables saving the child object.  When the child object i=
s=20
> saved, the parent is automatically saved.
>
> Shouldn't we have the child object saved only when the parent is sa=
ved=20
> (in the interface) ??
> What do you think ?
>
> Philippe
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, sec=
urity?
> Get stuff done quickly with pre-integrated technology to make your =
job=20
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache=
=20
> Geronimo
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057=
&dat=3D121642
> _______________________________________________
> Mdarad-toolbox-devs mailing list
> Mda...@li...
> https://lists.sourceforge.net/lists/listinfo/mdarad-toolbox-devs
>
>