Re: [Geoserver-users] Validate datastore configuration through REST API

2017-10-03 Thread Anton Bakker 
Hi Nuno,

Thanks for checking, I realise now that I configured datastores with a non 
existing schema, in that case GeoServer can connect to the DB but cannot find 
any featuretypes. So an empty list makes sense in that situation. When I 
misconfigured the datastore with wrong connection details the behaviour is 
indeed like you describe (with the unfortunate 404) for GeoServer 2.12. 

For GeoServer 2.10 I found some weird behavioural difference between list=all 
and list=available:

Invalid Oracle datastore (misconfigured port):

- featuretypes.xml?list=all RESPONSE: HTTP 200 OK, BODY: 
- featuretypes.xml?list=available RESPONSE: HTTP 500 SERVER ERROR, BODY: Could 
not load datastore: oracle:null

Invalid PostGIS datastore (misconfigured port):

- featuretypes.xml?list=all  RESPONSE: HTTP 200 OK, BODY: 
- featuretypes.xml?list=available RESPONSE: HTTP 500 SERVER ERROR, BODY: Could 
not load datastore: postgis:null

In case anyone else ever runs into this.

Kind regards,
Anton


Hi,

I just made a test with two types of data store (shapefile and postgis), and 
both fail with the exception (and an unfortunate 404 exception code,
it should be 500 IMHO) if the connection parameters are not correct:

Could not load datastore: 

Note that this will only fail if the *list=all* query parameter is provided, 
otherwise only the configured
layers for the data store will be listed and indeed in that case no exception 
will be returned (which is the correct behavior).

Please double check that you are targeting a data store with invalid connection 
parameters and using the
*list=all* query parameter and that no cache is happening. If you still don't 
see any exception message I will suggest you
to open a JIRA ticket describing the issue and how to reproduce it.

If you want to take a look at code you should look here:
I just made a test with two types of data store (shapefile and postgis), and 
both fail with the exception (and an unfortunate 404 exception code,
it should be 500 IMHO) if the connection parameters are not correct:

Could not load datastore: 

Note that this will only fail if the *list=all* query parameter is provided, 
otherwise only the configured
layers for the data store will be listed and indeed in that case no exception 
will be returned (which is the correct behavior).

Please double check that you are targeting a data store with invalid connection 
parameters and using the
*list=all* query parameter and that no cache is happening. If you still don't 
see any exception message I will suggest you
to open a JIRA ticket describing the issue and how to reproduce it.

If you want to take a look at code you should look here:
it should be 500 IMHO) if the connection parameters are not correct:

Could not load datastore: 

Note that this will only fail if the *list=all* query parameter is provided, 
otherwise only the configured
layers for the data store will be listed and indeed in that case no exception 
will be returned (which is the correct behavior).

Please double check that you are targeting a data store with invalid connection 
parameters and using the
*list=all* query parameter and that no cache is happening. If you still don't 
see any exception message I will suggest you
to open a JIRA ticket describing the issue and how to reproduce it.

If you want to take a look at code you should look here:
Could not load datastore: 

Note that this will only fail if the *list=all* query parameter is provided, 
otherwise only the configured
layers for the data store will be listed and indeed in that case no exception 
will be returned (which is the correct behavior).

Please double check that you are targeting a data store with invalid connection 
parameters and using the
*list=all* query parameter and that no cache is happening. If you still don't 
see any exception message I will suggest you
to open a JIRA ticket describing the issue and how to reproduce it.

If you want to take a look at code you should look here:
Could not load datastore: 

Note that this will only fail if the *list=all* query parameter is provided, 
otherwise only the configured
layers for the data store will be listed and indeed in that case no exception 
will be returned (which is the correct behavior).

Please double check that you are targeting a data store with invalid connection 
parameters and using the
*list=all* query parameter and that no cache is happening. If you still don't 
see any exception message I will suggest you
to open a JIRA ticket describing the issue and how to reproduce it.

If you want to take a look at code you should look here:
Note that this will only fail if the *list=all* query parameter is provided, 
otherwise only the configured
layers for the data store will be listed and indeed in that case no exception 
will be returned (which is the correct behavior).

Please double check that you are targeting a data store with invalid connection 
parameters and using the
*list=all* query

Re: [Geoserver-users] Labelling Geoserver Instances with Unique Names in Clustered Setup

2017-10-03 Thread Steve Omondi 
Wooow!

Thank you Andrea. I've really been looking for this except from the wrong
place.

This is great.

Kind regards,
Steve Omondi

On Tue, Oct 3, 2017 at 11:47 AM, Andrea Aime 
wrote:

> Hi Steve,
> it's actually a core functionality, see here:
>
> http://docs.geoserver.org/stable/en/user/production/identify.html
>
> Cheers
> Andrea
>
>
> On Tue, Oct 3, 2017 at 10:30 AM, Steve Omondi 
> wrote:
>
>> Hey guys,
>> I have 6 Geoserver instances (GS1, GS2,...GS6) behind Apache HTTPD Proxy.
>>
>> I'd like to Label these instances in the Web Admin GUI with the names so
>> that I know which instance the Load Balancer has redirected to.
>>
>> I have heard there is an extension which can help me do this but I can't
>> find it nor any documentation. What is the plugin? Could someone share with
>> me the link kindly?
>>
>> Kind regards,
>> Steve Omondi
>>
>>
>> 
>>  Virus-free.
>> www.avast.com
>> 
>> <#m_7367027973464436087_m_226570970404746240_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> Geoserver-users mailing list
>>
>> Please make sure you read the following two resources before posting to
>> this list:
>> - Earning your support instead of buying it, but Ian Turton:
>> http://www.ianturton.com/talks/foss4g.html#/
>> - The GeoServer user list posting guidelines:
>> http://geoserver.org/comm/userlist-guidelines.html
>>
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>>
>
>
> --
>
> Regards,
>
> Andrea Aime
>
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 
> 55054  Massarosa
> 
> (LU)
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39  339 8844549
>
> http://www.geo-solutions.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.
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Labelling Geoserver Instances with Unique Names in Clustered Setup

2017-10-03 Thread Andrea Aime 
Hi Steve,
it's actually a core functionality, see here:

http://docs.geoserver.org/stable/en/user/production/identify.html

Cheers
Andrea


On Tue, Oct 3, 2017 at 10:30 AM, Steve Omondi 
wrote:

> Hey guys,
> I have 6 Geoserver instances (GS1, GS2,...GS6) behind Apache HTTPD Proxy.
>
> I'd like to Label these instances in the Web Admin GUI with the names so
> that I know which instance the Load Balancer has redirected to.
>
> I have heard there is an extension which can help me do this but I can't
> find it nor any documentation. What is the plugin? Could someone share with
> me the link kindly?
>
> Kind regards,
> Steve Omondi
>
>
> 
>  Virus-free.
> www.avast.com
> 
> <#m_226570970404746240_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines: http://geoserver.org/comm/
> userlist-guidelines.html
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>


-- 

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.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.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] WMS GetFeatureInfo changes date value

2017-10-03 Thread Andrea Aime 
On Tue, Oct 3, 2017 at 10:31 AM, Nuno Oliveira <
nuno.olive...@geo-solutions.it> wrote:

> For the well behaved formats (GeoJson, GML 31 and GML 32) it is possible
> to control if GeoServer will or will not
> take into account the the time zone when encoding date \ time attributes
> using this Java property:
>
> -Dorg.geotools.localDateTimeHandling=true
>
> This will make GeoServer stop converting the data \ time to UTC-time,
> which should give you the results you are expecting.
>

Yep... would be nice to have that as a config flag in the UI (as opposed to
a system variable).
And yes, it's hard for many to come to terms to it, but dates do have a
timezone too, as I'm writing now
it's Tuesday here and in most of the world, but in Honolulu, it's still
Monday.

For international tenders there is even a special timezone used for
deadlines known as AOE (Anywhere
On Earth), when a date is chosen to be the deadline for presenting an
offer, it's often associated to AOE
to avoid the confusion of just stating a date:
https://en.wikipedia.org/wiki/Anywhere_on_Earth

Cheers
Andrea

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.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.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Labelling Geoserver Instances with Unique Names in Clustered Setup

2017-10-03 Thread Steve Omondi 
Hey guys,
I have 6 Geoserver instances (GS1, GS2,...GS6) behind Apache HTTPD Proxy.

I'd like to Label these instances in the Web Admin GUI with the names so
that I know which instance the Load Balancer has redirected to.

I have heard there is an extension which can help me do this but I can't
find it nor any documentation. What is the plugin? Could someone share with
me the link kindly?

Kind regards,
Steve Omondi


Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] WMS GetFeatureInfo changes date value

2017-10-03 Thread Nuno Oliveira 

Hi,

I made a few tests for this, GeoJson (this also stands for GML 3.1 and GML 3.2) 
have the correct default behavior,
i.e. they take into account the timezone when encoding a date \ time attribute.

The following formats: text/html, text/plain, text/xml and 
application/vnd.ogc.gml (GML2), don't have any special
treatment for date \ times and simply do a to string regardless of the timezone 
or time format. In my opinion this
is a bug and deserves a JIRA ticket (maybe one already exists).

In case someone wants to take a look at the code, for example the text/plain 
output format:
https://github.com/nmco/geoserver/blob/8d5c1dbc774e68baf445354bcb5e5fc2d5c122e3/src/wms/src/main/java/org/geoserver/wms/featureinfo/TextFeatureInfoOutputFormat.java#L106-L135

For the well behaved formats (GeoJson, GML 31 and GML 32) it is possible to 
control if GeoServer will or will not
take into account the the time zone when encoding date \ time attributes using 
this Java property:

   -Dorg.geotools.localDateTimeHandling=true

This will make GeoServer stop converting the data \ time to UTC-time, which 
should give you the results you are expecting.

Regards,

Nuno Oliveira

On 09/29/2017 02:09 PM, perre wrote:

Hi

If you sent a GetFeatureInfo-request to a layer that have a column with the
date-format in a PostGisDatabase, Geoserver sometimes add a time to the
date. This is a problem when it is changed into UTC-time and the date is
changed which happens with json.

INFO_FORMAT result
text/html  2017-06-01 00:00
text/plain 2017-06-01
text/xml   2017-06-01
application/vnd.ogc.gml2017-06-01
application/json  2017-05-31Z

Postgis (date)  2017-06-01




--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users



--
Regards,
Nuno Oliveira
==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V 
for more information.
==

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:  +39 0584 1660272

http://www.geo-solutions.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.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you

Re: [Geoserver-users] ImagePyramid using Postgresql for granules

2017-10-03 Thread Darell van der Voort 
Hello Daniele,

Thank you for the update, however I do not seem to get it to work. Please
let me know if i'm missing something. I start with the following initial
folder structure:

/geoserver/data/workspace//*.tiffs
/geoserver/data/workspace//datastore.properties
/geoserver/data/workspace//indexer.properties
/geoserver/data/workspace//1/*.tiffs
/geoserver/data/workspace//1/datastore.properties
/geoserver/data/workspace//1/indexer.properties
etc.

Note that in the initial folder structure there is no folder named '0', as
the imagepyramid only accepts folder structures as outputted by
gdal_retile. My datastore and indexer properties files look like:

*Datstore.properties:*
SPI=org.geotools.data.postgis.PostgisNGJNDIDataStoreFactory
schema=plantation_ecu_sumifru_144
Loose\ bbox=true
Estimated\ extends=false
validate\ connections=true
Connection\ timeout=10
preparedStatements=true
jndiReferenceName=java:comp/env/jdbc/postgis

*Indexer.properties:*
Caching=false
TimeAttribute=ingestion
Schema=*the_geom:Polygon,location:String,ingestion:java.util.Date:Double
PropertyCollectors=TimestampFileNameExtractorSPI[timeregex](ingestion)
TypeName=imagery0

Note the addition of 'TypeName' to the indexer.properties, which is unique
per folder level. Using this set-up Geoserver returns the following error:

file:///geoserver/data/testworkspace/imagery_pyramid/
java.lang.RuntimeException: Could not list layers for this store, an error
occurred retrieving them: null
at
org.geoserver.web.data.layer.NewLayerPageProvider.getItemsInternal(NewLayerPageProvider.java:158)
at
org.geoserver.web.data.layer.NewLayerPageProvider.getItems(NewLayerPageProvider.java:61)
at
org.geoserver.web.wicket.GeoServerDataProvider.fullSize(GeoServerDataProvider.java:243)
at
org.geoserver.web.wicket.GeoServerTablePanel$PagerDelegate.updateMatched(GeoServerTablePanel.java:583)
at
org.geoserver.web.wicket.GeoServerTablePanel$PagerDelegate.(GeoServerTablePanel.java:576)
at
org.geoserver.web.wicket.GeoServerTablePanel.(GeoServerTablePanel.java:176)
at
org.geoserver.web.wicket.GeoServerTablePanel.(GeoServerTablePanel.java:97)
at org.geoserver.web.data.layer.NewLayerPage$1.(NewLayerPage.java:105)
at org.geoserver.web.data.layer.NewLayerPage.(NewLayerPage.java:105)
at
org.geoserver.web.data.store.CoverageStoreNewPage.onSuccessfulSave(CoverageStoreNewPage.java:86)
at
org.geoserver.web.data.store.CoverageStoreNewPage.onSave(CoverageStoreNewPage.java:74)
at
org.geoserver.web.data.store.AbstractCoverageStorePage$1.onSubmit(AbstractCoverageStorePage.java:122)
at
org.apache.wicket.ajax.markup.html.form.AjaxSubmitLink$1.onSubmit(AjaxSubmitLink.java:111)
at
org.apache.wicket.ajax.form.AjaxFormSubmitBehavior$AjaxFormSubmitter.onSubmit(AjaxFormSubmitBehavior.java:215)
at org.apache.wicket.markup.html.form.Form.delegateSubmit(Form.java:1309)
at org.apache.wicket.markup.html.form.Form.process(Form.java:976)
at org.apache.wicket.markup.html.form.Form.onFormSubmitted(Form.java:797)
at
org.apache.wicket.ajax.form.AjaxFormSubmitBehavior.onEvent(AjaxFormSubmitBehavior.java:171)
at
org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:155)
at
org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:601)
at sun.reflect.GeneratedMethodAccessor427.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:258)
at
org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:241)
at
org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.invokeListener(ListenerInterfaceRequestHandler.java:248)
at
org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:234)
at
org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:895)
at
org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
at
org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:265)
at
org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:222)
at
org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:293)
at
org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:261)
at
org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:203)
at
org.apache.wicket.protocol.http.WicketServlet.doPost(WicketServlet.java:159)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:660)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
at
org.springframework.web.servlet.mvc.ServletWrappingController.handleRequestInternal(ServletWrappingController.java:158)
at
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:147)
at