Justin Deoliveira wrote:
> Jody Garnett wrote:
>> 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.
>>
> I don't think so. PropertyName is just an xpath expression, which may 
> have multiple namesapces / local parts associated with it. A single 
> name wont do it. I also see no such thing on the PropertyName interface.
So you need the raw xpath alone then - it includes the information you want?
>> If your GMLDataStore knows about such things as namespace you can 
>> make a special PropertyAccessor just for it that takes everything 
>> into account.
> Unfortunatley creation occurs at parsing time, and the parser has no 
> notion of a special datastore of sorts. To pull this off I would need 
> to be able to register PropertyAccessor instances dynamically at 
> runtime, which isn't really possible with our extension mechanism.
So we need to follow our own guideline of "injecting" these sorts of 
thing - to make the Filter evaluation context aware? Or is this a use 
case for Martin's might morphing power Hints?
> Also, the information needed to pull this off is only available while 
> the filter is being parsed. It isn't really around at evaluation time, 
> so hints wont really work either. 
Nasty; is their anyway Filter can take this information along for the 
ride? I see in your original request you talk about picking up all the 
namespaces available during parsing; can you show a code example about 
what that would do to our poor Filter api?

I am in conflict here:
- I would like to preserve the separation between query model (filter) 
and metadata model (schema) if we possibly can;
- I hate turning things into objects and having them forget all the 
stuff available during parsing (as in this case it comes in useful).

Straight up conflict; so I guess I need to know more... my slight hope 
is that the parser can be "greedy" and use the namespace information it 
has to disambiguate the property expression during the parse...
Jody

-------------------------------------------------------------------------
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

Reply via email to