Ciao MIlton,
sorry for the late answer.
Please, read below...
---
===
Notice that our office phone number has recently changed!
Please, update your records!
===
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Founder
Via Carignoni 51
55041 Camaiore
schemaURI ordering in app-schema mapping file shouldn't matter
--
Key: GEOT-3262
URL: http://jira.codehaus.org/browse/GEOT-3262
Project: GeoTools
Issue Type: Bug
Hi Niels; we really need to keep discussion on the email list (as while my
opinions may be helpful - they may not be correct).
You may indeed have found a hole in the api; performing the work in canHandle
method may still not be correct.
Here is another idea; modify the look up code to go
Thanks everyone for the help with GeoTools 2.7-M2; the workshop went very
smoothly.
Justin got a bit of testing in; and noticed that changing the CRS in the CRS
tutorial works ... but the map extents need to be updated. So by carefully
skipping that workbook for a coffee break everything was
I think your proposal is the most straight-forward way to solve the
issue without giving in on performance.
However, the property accessor shouldn't return null but throw an
exception if the property doesn't exist, because there still should be a
difference between an actual null value and a
However, looking at it, there is another issue.
AttributeExpressionImpl currently cashes its latest PropertyAccessor for
performance reasons (as scanning the registry is very expensive).
You can't do that anymore in the same way when we need to try multiple
property accessors. We couldn't
I would like to remove .gitignore from GeoTools trunk and 2.6.x.
Justin (see below) reports that, for GeoServer, he prefers to not have
.gitignore in the repo. Sounds like some other developers do the same.
Keeping .gitignore in the repo reminds me of keeping .project and
.classpath in the
