I am afraid you are damed if you do and dammed if you don't :-( Let's think - we could ask for a getCapabilities() method on WFSDataStore. It would need to take a ProgressListener .... so getCapabilities( ProgessListener ). Just going to check if the actual Capabilities object is public ... yes it is a public class WFSCapabilities.
Bleck - let's ask for Justin's input (he ported the catalog code over from uDig to GeoTools). If I were you I would use catalog right now (since you *can* use it right now) - and then plan to change that section of your code when GeoServer has figured out what it wants to see ... As far as I understand GeoServer would like to see: WFSService.getAbstract() Rather than: IService.getInfo( null ).getAbstract() If justin is actually planning to change things soon (ie in the next month) then we can make a bug report requesting WFSDataStore.getCapabilities( progressListener ). Cheers, Jody > Hi Jody, > > I remember this page about the catalogue from my previous question. Back > then you told me that it isn't "stable" enough and that I should stick to > the datastore API for now. > > It seems the catalogue will be quite an improvement for these issues > (metadata, etc) do you feel that it is better to adopt it has it is now than > subclassing WFSDataStore? > > Thanks for all the help > Tiago > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Geotools-gt2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
