[udig-devel] Can feature, created programmaticaly, has another ID than "newN"?

[Jody Garnett]

This is a tough one Sergiy - the ID is not valid until you call 
commit(). If you are adding a Feature to an external Web Feature Server 
we will not know it's ID until the server reports back to us.

I would like to move to the scenario where the commit() statement 
reports back the IDs of the newly added Features but have not yet 
managed it.
Jesse has done some hacks where we updates a the Set of FeatureIDs based 
on the commit notifications - but it really is a hack.

If there is a way for you not to use a FidFilter I recommend it.

Jody
> When we add features with AddFeatureCommand() it doesn't matter what
> is the featureID. The feature, added to map, will have "newN" (e.g.
> "new15") ID.
>
> But can we somehow create features with ID that we need?
>
> For example, I want to select M newly added features with FidFilter.
> What should I do - add "new0", "new1", ..., "newM" to FidFilter? It
> doesn't look very good.
> _______________________________________________
> User-friendly Desktop Internet GIS (uDig)
> http://udig.refractions.net
> http://lists.refractions.net/mailman/listinfo/udig-devel