[Geoserver-users] REST API Feature Type Creation

I have an workspace with multiple datastores meaning it has multiple database connections.so tableName can be same between the databases.

So the issue is now that when i try to create a featuretype using i have noticed that it creates a layer automatically and in my post data
the featureType name needs to be same as tablename.

so the first featureType from one datastore gets created fine
the second one from diffrerent datastore but same tablename get me error
saying the resource with same name already exists.

So how can i solve this?

Regards

Murad

Hi Jamal,
you should create the second feature type using the same nativeName (i.e. the table name in the DB), but a different name.

For example, let’s assume you have a my_feature table in two different datastores, ds1 and ds2. You can publish both with these commands:

publish my_feature table from datastore ds1

curl -v -u admin:geoserver -XPOST -H “Content-type: text/xml” -d “my_feature_1my_featurehttp://localhost:8080/geoserver/rest/workspaces/ws/datastores/ds1/featuretypes

publish my_feature table from datastore ds2

curl -v -u admin:geoserver -XPOST -H “Content-type: text/xml” -d “my_feature_2my_featurehttp://localhost:8080/geoserver/rest/workspaces/ws/datastores/ds2/featuretypes

Hope this helps.

···

On Thu, Oct 29, 2015 at 3:27 AM, Murad Jamal <muradjamal@anonymised.com> wrote:

I have an workspace with multiple datastores meaning it has multiple database connections.so tableName can be same between the databases.

So the issue is now that when i try to create a featuretype using i have noticed that it creates a layer automatically and in my post data
the featureType name needs to be same as tablename.

so the first featureType from one datastore gets created fine
the second one from diffrerent datastore but same tablename get me error
saying the resource with same name already exists.

So how can i solve this?

Regards

Murad



Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Best regards,
Stefano Costa

==
GeoServer Professional Services from the experts! Visit
[http://goo.gl/it488V](http://goo.gl/it488V) for more information.
==
Dott. Stefano Costa
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:     +39 0584 1660272

[http://www.geo-solutions.it](http://www.geo-solutions.it)
[http://twitter.com/geosolutions_it](http://twitter.com/geosolutions_it)

-------------------------------------------------------
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate.
Il loro utilizzo è consentito esclusivamente al destinatario del
messaggio, per le finalità indicate nel messaggio stesso. Qualora
riceviate questo messaggio senza esserne il destinatario, Vi preghiamo
cortesemente di darcene notizia via e-mail e di procedere alla
distruzione del messaggio stesso, cancellandolo dal Vostro sistema.
Conservare il messaggio stesso, divulgarlo anche in parte,
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità
diverse, costituisce comportamento contrario ai principi dettati dal
D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely
for the attention and use of the named addressee(s) and may be
confidential or proprietary in nature or covered by the provisions of
privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New
Data Protection Code).Any use not in accord with its purpose, any
disclosure, reproduction, copying, distribution, or either
dissemination, either whole or partial, is strictly forbidden except
previous formal approval of the named addressee(s). If you are not the
intended recipient, please contact immediately the sender by
telephone, fax or e-mail and delete the information in this message
that has been received in error. The sender does not give any warranty
or accept liability as the content, accuracy or completeness of sent
messages and accepts no responsibility  for changes made after they
were sent or for other risks which arise as a result of e-mail
transmission, viruses, etc.