Hmmm I don't seem able to edit it, even though I have 'developer'
membership in geotools codehaus.
Hmm...
On 17/12/10 15:19, Jody Garnett wrote:
Can you add that to the wiki page please;
And good to hear from you,
Jody
On 17/12/2010, at 3:56 PM, Niels wrote:
-------- Original Message --------
Subject: RE: namespaces part 2
Date: Wed, 15 Dec 2010 17:02:28 +0800
From: Charlier, Niels (CESRE, Kensington) <[email protected]>
To: Jody Garnett <[email protected]>
Hi Jody,
I think the ideas proposed are excellent, they are exactly what I need.
Just one more thing.
There needs to be some way to get the namespace context out of the
propertyname, too.
One of the issues I came across, was that of filter visitors that recreate the
filters. They cause the NameSpaceContext to be lost when they recreate the
PropertyNames with a new filterfactory.
They should recreate the property names with namespace context in it.
Perhaps this could be done by creating a subinterface of PropertyName,
NameSpaceAwarePropertyName, and then this could be done::
if (propName instanceof NameSpaceAwarePropertyName) {
return ff.propertyName (propName.getName(),
((NameSpaceAwarePropertyName)propName).getNameSpaceContext());
} else {
return ff.propertyName (propName.getName());
}
Thanks,
Niels
________________________________________
From: Jody Garnett [[email protected]]
Sent: Wednesday, December 15, 2010 8:29 AM
To: GeoTools Developers list
Cc: Charlier, Niels (CESRE, Kensington)
Subject: namespaces part 2
Okay Gabriel took an hour to chat with me through ... I was hoping we could do
more with xpath than the filter 1.1 spec allows us to.
FilterFactory2
- FilterFactoryImplNamespaceAware ideas to be merged into FilterFactory2 (and
thus part of our geotools api)
- FilterFactory2.property( xpath, context )
"Context"
- As for context; the implementation shows the Hint is made up of a single
NamespaceSupport class. Since this is a SAX class it may be hard to use for
people making up a context on the fly as part of a query?
- Gabriel looked at NamespaceContext instead; but is having a hard time finding
a good implementation
Query:
- getQueryHint should cover the use of a NamespaceSupport class as one of the
hints; allowing propertyNames to work
- or make an explicit Query.getNamespaceSupport() method to go with
getPropertyNames()
Neils I will send you our IRC chat.
Jody
------------------------------------------------------------------------------
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
--
*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
------------------------------------------------------------------------------
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
