I’m struggling to work out how I go from a DataStore (or just a file) to a layer in the catalog I can make a WFS request from. The manual page will voluminous doesn’t currently mention this and I can’t find an example of a test doing it either which probably means I’m on the wrong path
Datastore is supposed to isolate the web service from individual files; but you can probable figure it out anyways.
Go through the dataStores looking at the connection parameters for the file name in question (probably represented as a file URL
Once located you can check the datastore for its resources (should be FeatureTypes, or CoverageTypes, or …)
The resource name is the same as the layer name (we never did allow a resource to publish more than one layer although the separation is in the data model)
Datastore is supposed to isolate the web service from individual files; but you can probable figure it out anyways.
Go through the dataStores looking at the connection parameters for the file name in question (probably represented as a file URL
Once located you can check the datastore for its resources (should be FeatureTypes, or CoverageTypes, or …)
The resource name is the same as the layer name (we never did allow a resource to publish more than one layer although the separation is in the data model)
I’m not sure that works for what I’m trying to do.
I need to add a shapefile to the catalog so I can make a WFS request against it. I can’t find any tests that add more than a property file to the catalog so I’m stuck.
I cannot find an example in the existing tests, so I guess it should be done like GUI/REST do, in the “onSetup” method of a test…
that is, get a CatalogBuilder, and then use it to build one by one the StoreInfo, FeatureTypeInfo and LayerInfo.
WfsRemoteStoreTest follows the process in order to add a WFS cascading store and layer, you can mimic it for the shapefile case.
Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail