The GeoAPI interface should already have a method that accepts Name class (ie namespace plus localpart). You can choose to store both in our implementation and do as you see fit.
If your GMLDataStore knows about such things as namespace you can make a special PropertyAccessor just for it that takes everything into account. Jody > Hi all, > > I am working on getting actual xpath expressions to evaluate correctly > against our feature model. For instances "//gml:description" evaluates > to a "description" on a feature. > > My problem is that the PropertyName implementation (AttributeExpressionI > mpl) knows nothing about namespaces. What I would like is to create the > attribute expression with a namespace context which contains all the > namespace mappings present while parsing. > > Now I don't think that we need to change the PropertyName interface, > this is an implementation thing for sure. However, now we are creating > these things through the geoapi factory interface. > > I can think of two solutions: > > 1. Create a factory method to create a property with a namespace context: > > property( String xpath, NamespaceContext context ); > > 2. Use hints to pass a namespace context into the expression when it is > being evaluated. > > Anyone have any thoughts? > > -Justin > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
