[
http://issues.ops4j.org/browse/QI-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13304#action_13304
]
Rickard Öberg commented on QI-221:
----------------------------------
Falko, we did bring up the question of usecases for nested UoW on the mailing
list, so it's a shame you didn't speak up then. We removed it mainly because we
couldn't find a way to support it properly until v1.0, and opted to remove it
rather than to "sort of" have it.
You say that your system runs on a server, but is the nested UoW running on the
client? You mention transients, so it doesn't seem so. Also, are you using the
Swing UndoManager or something else? I think it could be entirely possible to
implement something specifically for clients using UndoManager, transients, and
value objects, so that the domain model on the server does not have to
understand undo\redo at all.
I'm very interested in supporting undo/redo management, but maybe we can do
something which is more client-specific, i.e. based on UndoManager and
transients/values rather than UoW/entities?
> Check nested UnitOfWork code so that it works properly.
> -------------------------------------------------------
>
> Key: QI-221
> URL: http://issues.ops4j.org/browse/QI-221
> Project: Qi4j
> Issue Type: Bug
> Reporter: Rickard Öberg
> Assignee: Rickard Öberg
> Priority: Critical
> Fix For: 1.0
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
