Hi all,
Recently this patch has been proposed:
http://jira.codehaus.org/browse/GEOT-3066
And this issue was discussed in detail on the mailing list some time ago in
this thread:
http://osgeo-org.1803224.n2.nabble.com/evaluating-invalid-attribute-names-td5489979.html
Apologies for not weighing in then. But I think this has some pretty serious
backward compatibility issues. The issue/proposal is to throw an exception
vs return null when a type has no such attribute described by an attribute
name or xpath, rather than return null. The thread above proposes to just
change the behaviour and update any test cases that rely on it. I could not
disagree more with his approach. This breaks backward compatibility and i
think requires more discussion. There is much more use of geotools beyond
test cases and even beyond geoserver and udig. If there is one thing i
learned at foss4g it is that there are lots of people using geotools, even
though they don't take parts in discussions on the developer list.
So i think this change requires more discussion and probably a proposal. And
it certainly can't take place on stable branch imo.
Is there any way we can have this behaviour engage only when the user
explicitly requests it? That has been a pattern that has worked very well in
the past for such changes.
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
