On Fri, Dec 17, 2010 at 9:03 AM, Niels <[email protected]> wrote: > I think you do need a NameSpace context in your query, because you cannot > assume that the namespace prefixes in the property names of the query are > the same as the ones in the mapping or in the datastore or anywhere else. > The thing about namespace prefixes is that you can never make those > assumptions. > Another solution for Query would be to provide a list of PropertyNames > rather than strings (which is what I suggested earlier I think?) but I guess > that would break too much existing code ?
Lucklily Query is not an interface anymore so it _would_ be possible to just add PropertyName (or Name) support and have it fall back on plain strings when the plain string methods are called. The new methods would be used only by code that know about complex features. Cheers Andrea ----------------------------------------------------- Ing. Andrea Aime Senior Software Engineer GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584962313 fax: +39 0584962313 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ----------------------------------------------------- ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
