Maybe not necessary for this case, but it can be good for youto know that we
have added support for using non persisten ValueObjects and
DataTransferObjects in the gui. By using these you can define a structure
that fits the GUI without necerarily having the same persistent domain
model.
/Patrik
greatfooty wrote:
>
>
>
> Andreas Källberg-2 wrote:
>>
>> Do you have an example model to show?
>> What if you model it with an 'artificial' container?
>>
>> Container {
>> ...
>> - List<@File> files
>> }
>> File {
>> String name
>> ...
>> }
>>
>> .../Andreas
>>
>>
>
> Many thanks Andreas that approach seems so obvious :thinking: .. and might
> be exactly what i need - in fact i do logically have a natural container
> which is 'Folder'. I hadn't modelled that as an entity but will consider
> this now.
>
>
>
--
View this message in context:
http://old.nabble.com/-Sculptor--Best-approach-for-handling-%27multiple%27-creates-or-updates--tp28571810s17564p28579544.html
Sent from the Fornax-Platform mailing list archive at Nabble.com.
------------------------------------------------------------------------------
_______________________________________________
Fornax-developer mailing list
Fornax-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fornax-developer
