On 24/12/10 13:32, Jody Garnett wrote:
To which idea is this +1 directed :-)
I am getting a bit nervous watching PropertyName being used as a placeholder for a
generic "qualified" XPath. Still I guess I understand why it is taking that
shape.
So is your +1 for the idea of:
Query.getAttributes(): List<PropertyName> // property name may refer to a
complete xpath
With this in mind getPropertyNames and setPropertyNames would then become a
shortcut methods for the above List.
Jody
There is one complication we neglected.
If we want to 'automatically' convert string to PropertyNames (for
backward compatibility)... we need a filter factory.
Query doesn't have access to a Filter Factory, and it can't use the
CommonFactoryFinder because it's in the gt-api package.
:(
--
*Niels Charlier*
Software Engineer
CSIRO Earth Science and Resource Engineering
Phone: +61 8 6436 8914
Australian Resources Research Centre
26 Dick Perry Avenue, Kensington WA 6151
------------------------------------------------------------------------------
Gaining the trust of online customers is vital for the success of any company
that requires sensitive data to be transmitted over the Web. Learn how to
best implement a security strategy that keeps consumers' information secure
and instills the confidence they need to proceed with transactions.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
