Additional information in case it helps: The issue may be related to either the names of the Shapefiles I am configuring or the number of them (> 350).
Shapefiles have a naming structure like "tile(-94_5047275__38_330816__-94_0047275__38_830816)_leisure_polygon.shp" I tried calling GeoServer's config reload via the REST interface and via the UI between the successful and unsuccessful runs but it didn't make a difference. The process I outlined in my last message works every time for a smaller list (15) of Shapefiles with more sensible names, e.g. leisure_polygon.shp so I'm fairly confident this is either a GeoServer problem or some issue with the number or files or their naming convention. -- View this message in context: http://osgeo-org.1560.n6.nabble.com/REST-create-data-store-NullPointerException-on-second-run-tp4987387p4987812.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
