HI Victor:
I am not sure the specific difference in ContentDataStore (rather than
AbstractDataStore) tripped up app schema. I assume it was the introduction
of call DataUtiltieis.simplify (which no doubt makes a copy using
DuplicatingFilterVisitor).
As per the patch Torben linked to we applied a
Hi Torben,
I apologize for the late reply, I just got back today from break. I am not
entirely sure what is the new property-ng implementation. Can you give me some
background on this? As Jody had mentioned, we lost Ben and Rini have gone on
maternity leave therefore we are slightly short on s
A workaround that will get app-schema working with ContentDataStore for the
geotools 13 release can be found here:
https://github.com/geotools/geotools/pull/678
A bug report for this issue can be found here:
https://jira.codehaus.org/browse/GEOT-4981
Torben
On Fri, Jan 9, 2015 at 12:56 PM, Jody
My first thought is to talk to the app schema module maintainer ... but
Rini is away. Victor and Lingbo have both been in recent communication
about build failures and may be in position to help.
My second thought is to ask for a bug report :)
A couple of random ideas:
- Fixing DuplicateFilterVis
I have managed to track down the cause of the error. Our
propertyNameResolving visitor (extending DuplicatingFilterVisitor) from
ContentFeatureSource.resolveProperty names ends up converting the
NestedAttributeExpression in our filter to an AttributeExpressionImpl by
way of the FilterFactoryImpl.pr
Hi Torben:
Ben was our usual contact for app schema stuff. Perhaps we can step through
the same test with the original property datastore implementation and see
how it was working (I won't claim to know how it was supposed to work).
Jody
--
Jody Garnett
On 8 January 2015 at 15:51, Torben Barsba
