<snip> > > So, let's try to sum up a possible action plan: > - add a style type field to StyleInfo > - add methods in StyleInfo to get and set the raw > style form (as i/o streams?) > - have a storage facility that recognizes the type > and knows what file to look for > - have a pluggable parser that knows how to parse > the contents coming from the storage into a GT2 > Style object. I am a little hesitant to start putting methods for doing I/O directly on the StyleInfo interface. I would like to try to keep config objects a s java bean like as possible.
But I think its a good idea to add those methods. What about putting them on ResourcePool? StyleInfo could still be a call through to ResourcePool, but client code wanting to change a style would have to go through RP. > > Hmm... actually the storage could be really dumb, > just know what the file name is and decouple > the parser from disk (database?) access. > > Opinions? > 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
