No, it is optional since not all datastores would be capable of handling associations.
Andrea added his hints for JTS_FACTORY and stuff to Hints. Shall I do th same? -Justin Jody Garnett wrote: > Andrea did some DataStore specific hints but I confess I do not > understand them and have not documented the result yet. I used to place > some properties on the transaction to accomplish the same effect. > > Given your story it sounds like this should be part of the Query? It is > a real requirement not an optional hint right? > Jody > >> Hi all, >> >> I am working on the wfs 1.1. xlink reference implementation in >> geoserver. Here is my use case: >> >> In a wfs query the client has the ability to set a "xlinkTraversalDepth" >> parameter which tells the wfs server how far to go while traversing >> associations among features. >> >> Now the way I have this implemented is that i need to pass this value to >> the underlying datastore. Seems like a good application of hints to me. >> >> So... long story short. I need a place to add a new well known Hint. Is >> the Hints class the place to do this. Or should we come up with some >> other class used to store well-known hints to be handled by datastores? >> >> -Justin >> >> > > > !DSPAM:4007,4746164c118553362379201! > -- Justin Deoliveira The Open Planning Project http://topp.openplans.org ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
