Andrea Aime wrote: > Justin Deoliveira ha scritto: >> Hi Andrea, >> >> This is an issue yes, and I think i know why it is happening. But >> first off, yes a collection should never be returned as null. And if >> you look at the implementation of any InfoImpl you should see that >> collections are always initialized with a value. The problem comes up >> with xstream persistance, because xstream does not use the constructor >> mechanism for creating the objects when it depersists. > > Right. Interesting, so, could the attach method we talked about > in a previous mail exchange be just a call to "resolve"? > What about making it public (just exploring options here). Yeah, I thought about this too as well. And while it would solve the problem that attach() is added for (ie, it sets the catalog on the object), the main purpose of resolve() is very implementation specific to the fact that we are using proxies. So I think in terms of what we make public, I think attach() makes more sense. Behind the scenes we can probably just have each attach() method call through to resolve(). > > Cheers > Andrea >
-- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
