Andrea Aime wrote: > Andrea Aime ha scritto: >> Works for me, we just have a handful of these cases, so I guess >> we can create reusable loadable/detachable models that know >> how to re-instate the lost attribute programmatically on reload? >> The candidates would be ResourceInfo and subclasses, by >> extension LayerInfo (since it holds a ResourceInfo), and >> AttributeTypeInfo? From what I can see all they need is to >> have the catalog set back in once deserialized? >> The loadable model could do this... > > Drawing some parallel with the way Hibernate works, what > about a: > Catalog.attach(Info info) > that does reconnect the impl with the catalog after it > has been deserialized. This has the advantage of not having > the UI code explicitly know about what needs to be done > and to make it stay away from the *Impl classes. Hmmm... I am not against it but I want to be sure we are not adding a method to the catalog interface just to get around an implementation detail. If we did have a hibernate catalog implementation, would a similar method be necessary? If so I am ok with adding it, if not I would say perhaps add it to the CatalogBuilder for now? > > 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
