The reason I ask is because committing like this works with the all
the datastores that are shipped with uDig. It seems that there are
some locks that are being held onto during commit. Could you run in
debug mode and when the deadlock occurs copy the stack trace. You
can send that to me that might provide me with some clues. Also send
me the log file that is generated by uDig when it happens. I don't
think the log will necessarily help in this case but you never know.
Jesse
On 3-Oct-06, at 3:30 AM, Francisco Javier García González wrote:
Hi Jesse,
Thanks for your feed-back. We are implementing our own
MyAbstractDataSatore that extends AbstractDataStore. We also
implements a MyFeatureWriter that implements FeatureWriter, and
within Write() method, we are invoking the
'AbstractDataStore.ListenerManager.FireFeatureChanged(typename,
transaction, bounds, true)' inherited method. We are not
overwriting the 'ListenerManager' at all, and this is the one that
hangs in 1.1.RC4 and not in previous ones.
Thansk again,
Javier.
Hi,
What datastore are you working with? PostGIS, WFS, Shapefile? Or
does it not matter what DS you are using. Also what type of changes
have you made?
Jesse
On 2-Oct-06, at 2:43 AM, Francisco Javier García González wrote:
Hello.
We are working with RC4 and eclipse 3.2.0, and when we call the
method map.getEditManager.Internal().commitTransaction(), UDIG
shows the message "Rendering <layer>" continually and it seems
that it is hung.
In RC2 this works fine.
Is there any way to call to commit directly?
thanks in advance.
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
