Yup, yet another place where datastores act differently. Doing it at the factory is a possibility, and yeah it would be something global which is nice. However the datastores would still have to do the work to actually figure out if the attribute is nillable.
However if speaking in strictly xml terms, i dont think that nillable implies that minOccurs = 0 as Xml has the notion of an explicit nil. However the wfs spec specifies that if an attribute instance is null you can just omit it, so the same behaviour. Again keep in mind that this is something that is undoubetly going to change with the new feature model, so gabriels feedback on how this is handled will be valuable. Andrea Aime wrote: > Justin Deoliveira ha scritto: >> Cool, patch looks great Andrea. > > The trouble is, what about the other data stores? > Shapefile won't work as in 1.5.x in Geoserver 1.6.0... > Plus there is oracle, db2, sde, and so on... > > Was thinking about it, the right thing to do seems > to make the attribute factory take care of this, since > it receives the "nillable" attribute, use it to determine > min occurrences without having to patch each datastore. > > Cheers > Andrea > > !DSPAM:1004,45f563b9131447785049143! > -- Justin Deoliveira The Open Planning Project http://topp.openplans.org ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
