Re: [Geoserver-devel] GSIP-176 Cite Automation update?
Sure, no problem. I found existing artifacts there and just reused the same location. Regards, Lorenzo Pini == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Lorenzo Pini 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 --- 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. On Wed, May 27, 2020 at 8:20 PM Jody Garnett wrote: > Some small feedback, as I went looking for test results. > > I noticed the jobs uploading to: > > https://repo.osgeo.org/repository/geotools-releases/org/opengis/cite/ets-wcs11/1.13/ets-wcs11-1.13-ctl.zip > > > Can you use the geoserver-releases repo for this work? I would also be > happy to make an additional repo if it is appropriate. > -- > Jody Garnett > > > On Fri, 22 May 2020 at 12:53, Jody Garnett wrote: > >> That is great, thank you for the update. >> >> While the other teams have setup osgeo docker facilities, you are the >> first to try from GeoServer. I would like to ensure you have sufficient >> access (via a PSC member) to manage next week. >> >> I am somewhat apprehensive, but looking forward to, seeing the initial >> testing results. >> -- >> Jody Garnett >> >> >> On Fri, 22 May 2020 at 09:45, Lorenzo Pini >> wrote: >> >>> Dear Jody, >>> I'm working on setting up the CITE tests automation. >>> >>> Here is a brief update on the current status: >>> - The required "ets-*" artifacts are being built on Jenkins. The deploy >>> phase is currently missing, but it is not blocking as we only have a single >>> server at the moment. >>> - The teamengine-docker image is being built on Jenkins. >>> - The cite-tests is now working on Jenkins and a first test shows that >>> the cite tests are able to run against the latest GeoServer master. >>> - I did a small improvement on the bash scripts to manage the exit code >>> but I think a change in the teamengine-core java code will be needed to >>> properly address this >>> >>> I'll continue next week with: >>> - Completing the deploy of all the artifacts and docker images in maven >>> repo and dockehub >>> - Improve the readability of the jobs logs >>> - Try the tests on different GeoServer releases >>> >>> Regards, >>> Lorenzo Pini >>> >>> == >>> GeoServer Professional Services from the experts! Visit >>> http://goo.gl/it488V for more information. >>> == >>> >>> Lorenzo Pini >>> 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 >>> --- >>> 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 >>> ad
Re: [Geoserver-devel] GSIP-176 Cite Automation update?
Dear Jody, I'm working on setting up the CITE tests automation. Here is a brief update on the current status: - The required "ets-*" artifacts are being built on Jenkins. The deploy phase is currently missing, but it is not blocking as we only have a single server at the moment. - The teamengine-docker image is being built on Jenkins. - The cite-tests is now working on Jenkins and a first test shows that the cite tests are able to run against the latest GeoServer master. - I did a small improvement on the bash scripts to manage the exit code but I think a change in the teamengine-core java code will be needed to properly address this I'll continue next week with: - Completing the deploy of all the artifacts and docker images in maven repo and dockehub - Improve the readability of the jobs logs - Try the tests on different GeoServer releases Regards, Lorenzo Pini == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Lorenzo Pini 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 --- 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. On Mon, Apr 6, 2020 at 8:53 PM Jody Garnett wrote: > Alessandro: > > We now have repo.osgeo.org operational, the builds should hopefully > switch over in the next couple of days. > > I have created https://repo.osgeo.org/repository/geoserver-docker/ for > you to try out. > -- > Jody Garnett > > > On Tue, 3 Mar 2020 at 09:48, Jody Garnett wrote: > >> For repo, would having an osgeo nexus repo help as a place to store the >> docker images? >> -- >> Jody Garnett >> >> >> On Tue, 3 Mar 2020 at 01:41, Alessandro Parma < >> alessandro.pa...@geo-solutions.it> wrote: >> >>> Thanks for your feedback >>> >>> My answers inline below >>> >>> > I think managing the docker builds in the "build" directory is >>> appropriate. Is it worth co-locating these with their cite data directory >>> configuration (to make each folder more self contained)? >>> >>> I agree. I would move the datadirs everything in the build/cite >>> <https://github.com/randomorder/geoserver/tree/gsip-176/build/cite> dir >>> along with the docker related file, ok? >>> >>> > aside: In the past when faced with builds grabbing status codes we >>> would grep through the output for failure, not sure how stable that is. >>> >>> Ok, thank you. I'll dig a little deeper into to try to avoid grepping >>> the logs, if possible. >>> >>> > There is not an official repository on docker hub for this, we should >>> set this up (I am not sure what is needed). >>> >>> I think we should create an Organization >>> <https://docs.docker.com/docker-hub/orgs/> and a team with members >>> allowed to push the docker image to the hub. >>> >>> On Fri, Feb 28, 2020 at 7:26 PM Jody Garnett >>> wrote: >>> >>>> Thank you for the update! >>>> >>>> I think managing the docker builds in the "build" directory is >>>> appropriate. Is it worth co-locating these with their cite data directory >>>> configuration (to make each folder more self contained)? >>>> >>>> aside: In the past when faced with builds grabbing status codes we >>>> would grep through the output for failure, not sure how stable that is. >>>> >>>> There is not an official repository on docker hub for this, we should >>>> set this up (I am not sure what is needed). >>>> -- >>>> Jod
[Geoserver-devel] Expired Certificate on Build Server
Hi all, the build server tls certificate expired on September the 2nd, who can fix it? https://build.geoserver.org/ Thank you Regards, Lorenzo Pini == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Lorenzo Pini 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 --- 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. ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Some libraries are not "SNAPSHOT" in the geoserver-master-latest.war
Dear all, today I found out the latest master war contains some libraries that are not "SNAPSHOT". They are: - gt-process-feature-20-20180403.122022-29.jar - gwc-gmaps-1.14-20180403.130115-41.jar Can I safely ignore them? Or is there the risk of getting outdated dependencies? Thank you Regards, Lorenzo Pini == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Lorenzo Pini 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-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] GeoServer Importer maximum running jobs
Dear all, I'm using the GeoServer importer and I noticed I can start as many sessions I want without receiving an error. Some of the sessions will simply go back to a "ready" state without having effect. After a little digging I foung this class: https://github.com/geoserver/geoserver/blob/master/src/extension/importer/core/src/main/java/org/geoserver/importer/job/JobQueue.java If I understand it correctly, the queue it's not actually queueing anything, it's a direct handoff, so the jobs will be executed immediatly until the thread pool reaches its maximum size. And since the maximum pool size is Integer.MAX_VALUE I guess I should not start too many sessions at once. If my findings are correct I'm going to open a JIRA to make the maximum number of concurrent jobs configurable. What do you think? Thank you Regards, Lorenzo Pini == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Lorenzo Pini 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-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-8145) Cascading WMS does not allow long credentials
Title: Message Title Lorenzo Pini created an issue GeoServer / GEOS-8145 Cascading WMS does not allow long credentials Issue Type: Bug Affects Versions: 2.6.2, 2.10.0, 2.10.3 Assignee: Unassigned Components: WMS Created: 18/May/17 9:40 PM Priority: Medium Reporter: Lorenzo Pini Due to GEOT-5731 a cascading WMS store cannot be configured if the combined username and password lenght is too big. To reproduce: Go to "Add New Store" -> "WMS - Cascades a remote Web Map Service" insert random name and url insert long username insert long password save org.apache.wicket.WicketRuntimeException: Exception 'Illegal character(s) in message header value: Basic dmVlZWVlZWVlZWVlZWVlZWVlZXJycnJycnJycnl5eXl5eXl5eXl5eXl5eXlsb29vb29vb29vb29v bmc6cGFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFh YWFhYWFhYWFhc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzd3d3d3d3d3d3d3d3d3d3d3d3d3d3 d3d3d3d3d29yZA==' occurred during validation org.geoserver.web.data.store.WMSStoreNewPage$WMSCapabilitiesURLValidator on component 7:form:capabilitiesURL:border:border_body:paramValue at org.apache.wicket.markup.html.form.FormComponent.validateValidators(
[Geoserver-devel] [JIRA] (GEOS-8129) GetLegendGraphic fails if SCALE is greater than MaxScaleDenominator
Title: Message Title Lorenzo Pini created an issue GeoServer / GEOS-8129 GetLegendGraphic fails if SCALE is greater than MaxScaleDenominator Issue Type: Bug Affects Versions: 2.10.4 Assignee: Unassigned Created: 08/May/17 2:27 PM Environment: Linux 64bit, Java Oracle 1.8.0, Tomcat 7, GeoServer 2.10-snapshot ( 70b43aa9e8d6d3f6576a73620a9dc5821febb2ad ) DuctusRenderingEngine No JAI Priority: Medium Reporter: Lorenzo Pini If a style has a Rule with and no other rule to match scales over it, the GetLegendGraphic fails with an Exception when a greater scale is requested. Example, all the rules in the style "poi" have 32000 If the requested scale matches the limit, it gives you an image: http://demo.geo-solutions.it/geoserver/wms?service=WMS=GetLegendGraphic=image%2Fpng=12=12=tiger%3Apoi==1.3.0_VERSION=1.1.0=32000 Otherwise an Exception: http://demo.geo-solutions.it/geoserver/wms?service=WMS=GetLegendGraphic=image%2Fpng=12=12=tiger%3Apoi==1.3.0_VERSION=1.1.0=32001 "http://www.opengis.net/ogc" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.3.0" xsi:schemaLocation="http://www.opengis.net/ogc http://demo.geo-solutions.it:80/geoserver/schemas/wms/1.3.0/exceptions_1_3_0.xsd"> java.lang.IllegalArgumentException: Width (2) and height (0) must be > 0 Width (2) and height (0) must be > 0
[Geoserver-devel] [JIRA] (GEOS-8060) Wicket error reloading feature type from JNDI
Title: Message Title Lorenzo Pini created an issue GeoServer / GEOS-8060 Wicket error reloading feature type from JNDI Issue Type: Bug Affects Versions: 2.9.5 Assignee: Unassigned Components: Wicket UI Created: 31/Mar/17 11:45 AM Priority: Medium Reporter: Lorenzo Pini A layer is published froma Oracle NG (JNDI) store. The layer is disabled Click on "Reload feature type", nothing happen Click on the Warning icon on the right of "Reload feature type", a warning message appears. Close the popup, the following message is shown. java.lang.RuntimeException: Could not deserialize object from byte[] at org.apache.wicket.serialize.java.JavaSerializer.deserialize(JavaSerializer.java:143) at org.apache.wicket.pageStore.AbstractPageStore.deserializePage(AbstractPageStore.java:152) at org.apache.wicket.pageStore.AbstractCachingPageStore.getPage(AbstractCachingPageStore.java:67) at org.apache.wicket.page.PageStoreManager$SessionEntry.getPage(PageStoreManager.java:203) at org.apache.wicket.page.PageStoreManager$PersistentRequestAdapter.getPage(PageStoreManager.java:357) at org.apache.wicket.page.AbstractPageManager.getPage(AbstractPageManager.java:82) at org.apache.wicket.page.PageManagerDecorator.getPage(PageManagerDecorator.java:50) at org.apache.wicket.page.PageAccessSynchronizer$2.getPage(PageAccessSynchronizer.java:246) at org.apache.wicket.DefaultMapperContext.getPageInstance(DefaultMapperContext.java:113) at org.apache.wicket.core.request.handler.PageProvider.getStoredPage(PageProvider.java:299) at org.apache.wicket.core.request.handler.PageProvider
[Geoserver-devel] [JIRA] (GEOS-7452) Process Status page do not refresh after a dismiss
Title: Message Title Lorenzo Pini created an issue GeoServer / GEOS-7452 Process Status page do not refresh after a dismiss Issue Type: Bug Affects Versions: 2.8.2 Assignee: Unassigned Components: Wicket UI Created: 09/Mar/16 3:51 PM Environment: GeoServer 2.8.2 with WPS and MBTiles plugins Chrome Browser Priority: Medium Reporter: Lorenzo Pini Hi, I started an MBTiles process and let it run for a while. When I wanted to dismiss it I went to the "Process Status" page in the GeoServer web UI. The process was dismissed but the page did not refresh. I had to reload the page to see the empty processes list To reproduce: Start a WPS process Open the "Process Status" page Select a process and click "Dismiss selected processes" Confirm the dismiss. The expected behaviour is: The process list is updated without the dismised process The current behaviour is: Th
[Geoserver-devel] [JIRA] (GEOS-7342) LayerGroup chooser in the LayerGroup page suggests LGs from other workspaces
Title: Message Title Lorenzo Pini created an issue GeoServer / GEOS-7342 LayerGroup chooser in the LayerGroup page suggests LGs from other workspaces Issue Type: Improvement Affects Versions: 2.6.3 Assignee: Unassigned Components: Wicket UI Created: 11/Dec/15 4:47 PM Labels: LayerGroup Workspace Priority: Low Reporter: Lorenzo Pini Use case: Create a workspace "A" Create a Layer Group "LGA" (in workspace A) Create a workspace "B" Create a Layer Group "LGB" Select workspace B Select "Add Layer Group..." The LGA layergroup is displayed and can be selected Save The Save fails with the error: Layer group within a workspace (B) can not contain resources from other workspace: A
[Geoserver-devel] [JIRA] (GEOS-7220) Document GetFeatureInfo on layergroup
Title: Message Title Lorenzo Pini created an issue GeoServer / GEOS-7220 Document GetFeatureInfo on layergroup Issue Type: Task Assignee: Unassigned Components: Documentation Created: 28/Sep/15 3:33 PM Priority: Low Reporter: Lorenzo Pini Document GetFeatureInfo behaviour on layergroups. Related to GEOS-6340 Add Comment This message was sent by Atlassian JIRA (v7.0.0-OD-07-011#70107-sha1:db940e9
[Geoserver-devel] [JIRA] (GEOS-7106) WFS DescribeFeatureType NPE with misconfigured layers
Title: Message Title Lorenzo Pini created an issue GeoServer / GEOS-7106 WFS DescribeFeatureType NPE with misconfigured layers Issue Type: Bug Affects Versions: 2.6.4 Assignee: Unassigned Components: WFS Created: 14/Jul/15 1:29 PM Environment: Version 2.6.4 Git Revision e522cb760457751b496e42b1169f8a344f934849 Running on Tomcat 6 Java OpenJDK 64-Bit Server VM 1.7.0_79 Priority: Low Reporter: Lorenzo Pini An SQL View can be configured to have spaces in the Attributes names. WFS DescribeFeatureType call fails with a java.lang.NullPointerException on such layers. To reproduce, create an SQL View with aliases and spaces names: SELECT prop1 AS Prop with spaces, geom from my_table; Publish
[Geoserver-devel] [JIRA] (GEOS-7082) WFS Content-Type cannot include charset
Title: Message Title Lorenzo Pini created an issue GeoServer / GEOS-7082 WFS Content-Type cannot include charset Issue Type: Bug Affects Versions: 2.6.4 Assignee: Unassigned Components: WFS Created: 19/Jun/15 5:01 PM Environment: Debian 7 wheezy Tomcat 6.0.41 GeoServer 2.6.4 AuthKey plugin WPS plugin Excel plugin Priority: Medium Reporter: Lorenzo Pini The requests issued to the WFS service with the Content-Type: application/x-www-form-urlencoded; charset=UTF-8 header are not recognized as form and parsed as XML resulting in a failure. Answer is: ows:Exception exceptionCode=NoApplicableCode ows:ExceptionTextorg.xmlpull.v1.XmlPullParserException: only whitespace content allowed before start tag and not s (position: START_DOCUMENT seen s... @1:1) only whitespace content allowed before start tag and not s (position
[Geoserver-devel] [jira] (GEOS-6899) Filter Chain Editing does not work
Title: Message Title Lorenzo Pini created an issue GeoServer / GEOS-6899 Filter Chain Editing does not work Issue Type: Bug Affects Versions: 2.6.2 Assignee: Andrea Aime Components: Security Created: 20/Feb/15 8:53 AM Labels: security authentication authorization Priority: Major Reporter: Lorenzo Pini In the Filter Chain page ( geoserver/web/?wicket:interface=:87 ) I'm trying to set up a new Chain filter by moving it from the Available box to the Selected box. In the interface it works and a POST is sent with the correct values and ordering: authFilterChain:recorder geostore,basic,anonymous After the change GeoServer does not react as expected and inspecting the security/config.xml file I see that the geostore filter is missing. ... filters name=default class=org.geoserver.security.ServiceLoginFilterChain interceptorName=interceptor exceptionTranslationName=exception path=/** disabled=false allowSessionCreation=false ssl=false matchHTTPMethod=false filterbasic/filter filteranonymous/filter /filters
[Geoserver-devel] [jira] (GEOS-6798) Saving layer after an SQL view edit causes WicketRuntimeException
Title: Message Title Lorenzo Pini created an issue GeoServer / GEOS-6798 Saving layer after an SQL view edit causes WicketRuntimeException Issue Type: Bug Affects Versions: 2.4.8 Assignee: Andrea Aime Components: Wicket UI Created: 11/Dec/14 10:07 AM Environment: CentOS 6 GeoServer 2.4.8 JAVA: Oracle Corporation: 1.7.0_65 (OpenJDK 64-Bit Server VM) Priority: Minor Reporter: Lorenzo Pini I had an SQL view without an identifier, so I edited the SQL statement to include another field and setted it as Identifier. The Edit SQL view page save when fine. The Edit Layer page save returned this stack trace. Reopening the layer showed no problem, the data was updated correcly. org.apache.wicket.WicketRuntimeException: Method onFormSubmitted of interface org.apache.wicket.markup.html.form.IFormSubmitListener targeted at component [MarkupContainer [Component id = resource]] threw an exception at org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:193
