Andrea Aime wrote: > Hi, > I'm having some troubles with the catalog objects I'd like > to discuss. > > There are a few catalog objects that do require some access > to GT2 provided information. For example, FeatureTypeInfo > can return a FeatureType, AttributeTypeInfo an AttributeDescriptor. > The way things are done now, that information provided > by some external entity during the object construction. > > Which works fine only as long as the object is serialized > and deserialized... which happens when those objects are > used within Wicket models. Now, for pure editing a form > can be backed by a loadable/detachable model that will > grab again the same FeatureTypeInfo from the catalog, > it's more work, but it's doable. Question, I thought we abandoned using straight serialization for catalog objects and instead adopted loadable detachable models, or is this just in some cases? > > What about a form that is editing a new FeatureTypeInfo > thought? That one is not in the catalog still, but > the FTI will be serialized as the page changes, and > if the user goes back, boom, the FTI gets deserialized, > but the FeatureType it contained is gone... > > So, how to deal with it? Ideas: > 1) Make those object talk to the catalog (make them > a bit more active) > 2) Mark a few properties as unsafe to use in the UI, > and build models that know how to handle them? > Let me know > I don't think I quite understand option 1, but I think I prefer option 2, with perhaps a spin:
a) omit properties that require the external resources, making them available only on an edit, or: b) if the property is necessary on the new form, create a model that loads it "manually", ie not through the feature type. This is more or less what the old stuff did to get around this i believe > 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
