[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [udig-devel] transaction freeze
|
Bleck; that sounds like a deadlock. You should be able to "pause" in the debugger and see what threads are waiting; I am not the best at untangling such things :-(
The commit dialog should be a two phase thing; the first command pops up the dialog; and then the dialog should issue a command that does all the work in the background (can you start by stepping through this process with the debugger and watching when it gets stuck?).
Aside: If we really get stuck and cannot untangle our deadlock we could simplify the problem (prevent user interaction during commit by using a modal commit dialog with the confirmation starting a progress bar...).
Jody
On 27/08/2010, at 9:55 PM, andrea antonello wrote:
> I have a problem with a transaction triggered from the form editor I
> am writing for shapefiles.
>
> What happens is that:
> - if I modify a value in the usual feature table and then commit,
> everything works as it should
> - if I modify with the form view, and the substitute and write the
> modified feature through:
>
> CompositeCommand compComm = new CompositeCommand();
> compComm.getCommands().add(EditCommandFactory.getInstance().createSetEditFeatureCommand(editedFeature));
> compComm.getCommands().add(EditCommandFactory.getInstance().createWriteEditFeatureCommand());
> context.getMap().sendCommandSync(compComm);
>
> Then, as soon as I push the commit button, the commit dialog opens and
> stays there forever. Gui is frozen and committ hangs somewhere. I am
> debugging through it and it seems to be in a nirvana inside the
> DefaultTransaction class.
>
> Anyone any idea about how to solve that or why it is happening?
>
> Ciao
> Andrea
> _______________________________________________
> User-friendly Desktop Internet GIS (uDig)
> http://udig.refractions.net
> http://lists.refractions.net/mailman/listinfo/udig-devel
