Hi Niels; I did gradually sort out (well in conversation with aaime) that it was as part of a longer xpath expression you were having trouble.
How does the xpath specification handle this? It was our intension to just use xpath and let the jxpath implementation sort out the details? At the very least it should be able to parse it into a data structure you can negotiate in greater details if needed. Jody On 06/12/2010, at 1:58 PM, Niels wrote: > Hi, > > Sorry for my late reply as I was on leave. > > I think you are misunderstanding. I am trying to create expressions based on > nested x-paths, that means it contains different steps of which each have > their own namespace prefix. A 'Name' object can only contain one of such > steps. > > Regards > Niels > > On 26/11/10 22:33, Jody Garnett wrote: >> >> The Name class is supposed to handle what you are doing; if not please let >> me know and we can fix it :-) >> >> We introduced the Name interface when String was no longer cutting it; but >> yeah give it a once over and let me know if does the job for you. >> >> The other interesting aspect of your email was the idea of feeding a hint >> into the factory. >> >> In general we don't want the factory to be stateful (instead we wrap a >> builder around it to be helpful and insert magic as needed). >> >> Constructing it with a hint would actually work - at least the state would >> not change at runtime which would make it safe to use. >> >> Before you take that approach please consider the use of Name; it is already >> there in order to encourage the gradual adoption of namespace. >> >> Jody >> >> On 26/11/2010, at 5:46 PM, Niels wrote: >> >>> On 26/11/10 15:21, Jody Garnett wrote: >>>> >>>>> We should be able to create a Property filter with a complete Name >>>>> (rather than a String) and thus store the namespace information). Are >>>>> you sure this is not already possible? >>>>> >>>> Checking the java docs for filter factory: >>>> PropertyName property(Name name) >>>> PropertyName property(String name) >>>> >>>> So you should be able to create a filter that supports namespace right >>>> now. >>> No, what I mean is to create an expression based on an x-path, not on a >>> name. >>> An x-path contains prefixes rather than namespace URI's and is nested. >>> In a filter on complex features one should be able to fill in a nested >>> x-path as filtering attribute rather than a property name. >>> >>> >>> -- >>> 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 >> > > > -- > 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
------------------------------------------------------------------------------
_______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
