On 2013-01-14 10:50, Andrea Aime wrote:
On Mon, Jan 14, 2013 at 10:14 AM, Matthijs Laan
<[email protected] <mailto:[email protected]>> wrote:
On 2013-01-12 21:28, Andrea Aime wrote:
>
> All the issues could be referred to a single cause:
> the SimpleFeaturePropertyAccessorFactory
> uses a regular expression to match valid property patterns that
is way
> too strict
> for real world, valid simple feature elements: it did not
consider the
> possibility
> of having dots, or accented chars, or dashes and the like in the
name,
> nor having
> the indexed access referring to the first instance, e.g.,
attribute[1].
Ah, so my workaround for special characters in property names in CQL
would no be longer needed? Ie.
ff.property("./*[name()='#SHAPE#']").evaluate(feature) to get the
value
of a property with special characters in its name.
Nope, since #SHAPE# is not a valid XML element name.
E.g. with something like:
<?xml version="1.0" encoding="UTF-8"?>
<container>
<#test#>
</#test#>
</container>
the eclipse XML validator states the document is not well formed
You're right, it's not valid in XML. I'm just used to any string in Java
when building a feature property or PostgreSQL database column names
which can contain more special characters than XML elements, and if you
stay in code/sql it may keep working with those. BTW I don't need the
JXPath workaround for this so I don't mind if its removed.
Thanks
Matthijs
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
