Hi again,

I have a question on MemoryDataStore persistence between sessions (or
whatever the term for quitting uDig, saving workspace and loading it
again).

Since the MemoryDataStore shows up in the Catalog with the layers that
existed before quitting (but with all features gone when doing Feature
Count and CRS unknown when doing Resource Summary), I figure there must
be some persistence after all.

When in the second session, I check the Catalog and get a
MemoryServiceImpl as "resolve" and it turns out that it can not resolve
to a IService, and not resolve to a DataStore. The same goes for my
WFSServiceImpl so I guess there is nothing strange with that.

However, the MemoryServiceImpl can resolve to a MemoryDataStore. So the
question is, how do I get to pick up that MemoryDataStore and use it as
an IService like I did in the previous session? It doesn't seem to be
able to adapt itself to a IService....

Thanks for any help!

Jonas


_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel

Reply via email to