[Geoserver-devel] [JIRA] (GEOS-10221) GeoServer Doc index page is outdated
Torben Barsballe ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A90497b76-fb66-4619-ae3c-49a316ab3d68 ) *created* an issue GeoServer ( https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiY2FjMjg3MmM2ZGRiNDRkZThmNGJlOWViYmMyZmI0ZDgiLCJwIjoiaiJ9 ) / Task ( https://osgeo-org.atlassian.net/browse/GEOS-10221?atlOrigin=eyJpIjoiY2FjMjg3MmM2ZGRiNDRkZThmNGJlOWViYmMyZmI0ZDgiLCJwIjoiaiJ9 ) GEOS-10221 ( https://osgeo-org.atlassian.net/browse/GEOS-10221?atlOrigin=eyJpIjoiY2FjMjg3MmM2ZGRiNDRkZThmNGJlOWViYmMyZmI0ZDgiLCJwIjoiaiJ9 ) GeoServer Doc index page is outdated ( https://osgeo-org.atlassian.net/browse/GEOS-10221?atlOrigin=eyJpIjoiY2FjMjg3MmM2ZGRiNDRkZThmNGJlOWViYmMyZmI0ZDgiLCJwIjoiaiJ9 ) Issue Type: Task Assignee: Torben Barsballe ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A90497b76-fb66-4619-ae3c-49a316ab3d68 ) Components: Documentation Created: 01/Sep/21 12:15 AM Priority: Medium Reporter: Torben Barsballe ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A90497b76-fb66-4619-ae3c-49a316ab3d68 ) The GeoServer Documentation landing page (docs.geoserver.org) is outdated. Furthermore, it is not tracked in version control, meaning that there is no way of updating it at this time. I suggest we: 1) Add it to the GeoServer github repository. Since it is a disambiguation page for all versions of our documentation (and since the only existing version of the page is pure html), it should live outside of the sphinx build tree - probably at either /doc/index.html or /doc/en/index.html 2) Update the GeoServer master doc build (and only master) to also push this file to the doc server. No need to create a new build just to deploy this file, even if it technically isn't part of the master docs. ( https://osgeo-org.atlassian.net/browse/GEOS-10221#add-comment?atlOrigin=eyJpIjoiY2FjMjg3MmM2ZGRiNDRkZThmNGJlOWViYmMyZmI0ZDgiLCJwIjoiaiJ9 ) Add Comment ( https://osgeo-org.atlassian.net/browse/GEOS-10221#add-comment?atlOrigin=eyJpIjoiY2FjMjg3MmM2ZGRiNDRkZThmNGJlOWViYmMyZmI0ZDgiLCJwIjoiaiJ9 ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495=EmailNotificationLink=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175- sha1:92848a8 )___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-9864) Document that major dependency upgrades should be treated as API changes when backporting
Torben Barsballe ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A90497b76-fb66-4619-ae3c-49a316ab3d68 ) *created* an issue GeoServer ( https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiNjhjMGZiYzFmODAzNDI3Zjk3YTdiMzFmNjMxYjRhOGMiLCJwIjoiaiJ9 ) / Improvement ( https://osgeo-org.atlassian.net/browse/GEOS-9864?atlOrigin=eyJpIjoiNjhjMGZiYzFmODAzNDI3Zjk3YTdiMzFmNjMxYjRhOGMiLCJwIjoiaiJ9 ) GEOS-9864 ( https://osgeo-org.atlassian.net/browse/GEOS-9864?atlOrigin=eyJpIjoiNjhjMGZiYzFmODAzNDI3Zjk3YTdiMzFmNjMxYjRhOGMiLCJwIjoiaiJ9 ) Document that major dependency upgrades should be treated as API changes when backporting ( https://osgeo-org.atlassian.net/browse/GEOS-9864?atlOrigin=eyJpIjoiNjhjMGZiYzFmODAzNDI3Zjk3YTdiMzFmNjMxYjRhOGMiLCJwIjoiaiJ9 ) Issue Type: Improvement Assignee: Unassigned Components: Documentation Created: 15/Jan/21 8:34 PM Priority: Medium Reporter: Torben Barsballe ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A90497b76-fb66-4619-ae3c-49a316ab3d68 ) Update the Community Process documentation to classify major dependency upgrades as API changes for the purposes of backporting, as per discussion during the Jan 5, 2021 PMC meeting ( http://osgeo-org.1560.x6.nabble.com/GT-GS-GWC-PMC-PSC-meeting-notes-January-5th-2021-td5454022.html ) The aim here is to avoid including API breaking changes in shared dependencies of GeoTools/GeoServer and downstream projects (like GeoMesa) during stable and maintenance point releases. Security fixes may still introduce API changes in dependencies, if necessary. ( https://osgeo-org.atlassian.net/browse/GEOS-9864#add-comment?atlOrigin=eyJpIjoiNjhjMGZiYzFmODAzNDI3Zjk3YTdiMzFmNjMxYjRhOGMiLCJwIjoiaiJ9 ) Add Comment ( https://osgeo-org.atlassian.net/browse/GEOS-9864#add-comment?atlOrigin=eyJpIjoiNjhjMGZiYzFmODAzNDI3Zjk3YTdiMzFmNjMxYjRhOGMiLCJwIjoiaiJ9 ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495=EmailNotificationLink=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100154- sha1:2a567c9 )___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-9543) GeoServer REST documentation: Parser error duplicated mapping key
Torben Barsballe ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A90497b76-fb66-4619-ae3c-49a316ab3d68 ) *created* an issue GeoServer ( https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiZDk2NzY5MWJjYzQ1NDFiYzgzNDMwYWMyMWZjZWU3MmUiLCJwIjoiaiJ9 ) / Improvement ( https://osgeo-org.atlassian.net/browse/GEOS-9543?atlOrigin=eyJpIjoiZDk2NzY5MWJjYzQ1NDFiYzgzNDMwYWMyMWZjZWU3MmUiLCJwIjoiaiJ9 ) GEOS-9543 ( https://osgeo-org.atlassian.net/browse/GEOS-9543?atlOrigin=eyJpIjoiZDk2NzY5MWJjYzQ1NDFiYzgzNDMwYWMyMWZjZWU3MmUiLCJwIjoiaiJ9 ) GeoServer REST documentation: Parser error duplicated mapping key ( https://osgeo-org.atlassian.net/browse/GEOS-9543?atlOrigin=eyJpIjoiZDk2NzY5MWJjYzQ1NDFiYzgzNDMwYWMyMWZjZWU3MmUiLCJwIjoiaiJ9 ) Issue Type: Improvement Assignee: Unassigned Created: 17/Mar/20 10:35 PM Priority: Medium Reporter: Torben Barsballe ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A90497b76-fb66-4619-ae3c-49a316ab3d68 ) Several pages from the GeoServer REST Documentation ( https://docs.geoserver.org/stable/en/user/rest/index.html ) give the error Parser error duplicated mapping key. This appears to be caused by the fix ( https://github.com/geoserver/geoserver/pull/4116 ) for GEOS-9533 ( https://osgeo-org.atlassian.net/browse/GEOS-9533 ) Open ( https://osgeo-org.atlassian.net/browse/GEOS-9543#add-comment?atlOrigin=eyJpIjoiZDk2NzY5MWJjYzQ1NDFiYzgzNDMwYWMyMWZjZWU3MmUiLCJwIjoiaiJ9 ) Add Comment ( https://osgeo-org.atlassian.net/browse/GEOS-9543#add-comment?atlOrigin=eyJpIjoiZDk2NzY5MWJjYzQ1NDFiYzgzNDMwYWMyMWZjZWU3MmUiLCJwIjoiaiJ9 ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495=EmailNotificationLink=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100122- sha1:87fe5bb )___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-9416) Use OpenJDK for release builds instead of Oracle
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-9416 Use OpenJDK for release builds instead of Oracle Issue Type: Improvement Assignee: Unassigned Created: 27/Nov/19 10:10 PM Priority: Medium Reporter: Torben Barsballe GeoServer has historically used Oracle Java for building release artifacts. There have been some recent issues with the availability of certain version of Oracle Java on Jenkins, possibly due to [https://issues.jenkins-ci.org/browse/JENKINS-57090JENKINS-57090) This, coupled with the increasing popularity OpenJDK over Oracle suggests we should use OpenJDK instead (or at least use it as the default - we can still keep the Oracle installer and have it as an option). Tasks: Update release scripts / defaults to match OpenJDK 8 version numbers Update Jenkins config for release jobs with correct version numbers Add Comment
[Geoserver-devel] [JIRA] (GEOS-9370) NPE with multidimensional GRIB2 file with time and custom dimension
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-9370 NPE with multidimensional GRIB2 file with time and custom dimension Issue Type: Improvement Assignee: Unassigned Components: Grib, NetCDF Created: 18/Oct/19 12:28 AM Priority: Medium Reporter: Torben Barsballe When loading GRIB2 files downloaded from the National Hurricane Center forcast data ( https://ftp.nhc.ncep.noaa.gov/wsp/ ), I get a NPE from within the NetCDF parser: Caused by: java.lang.NullPointerException at org.geotools.coverage.io.netcdf.NetCDFResponse.loadRaster(NetCDFResponse.java:772) at org.geotools.coverage.io.netcdf.NetCDFResponse.processRequest(NetCDFResponse.java:299) at org.geotools.coverage.io.netcdf.NetCDFResponse.createResponse(NetCDFResponse.java:145) at org.geotools.coverage.io.netcdf.NetCDFSource.read(NetCDFSource.java:65) at org.geotools.coverage.io.netcdf.NetCDFReader.read(NetCDFReader.java:506) at org.geoserver.catalog.SingleGridCoverage2DReader.read(SingleGridCoverage2DReader.java:146) at org.geoserver.catalog.CatalogBuilder.getCoverageSampleDimensions(CatalogBuilder.java:1154) at org.geoserver.catalog.CatalogBuilder.buildCoverageInternal(CatalogBuilder.java:1030) at org.geoserver.catalog.CatalogBuilder.buildCoverage(CatalogBuilder.java:951) at org.geoserver.catalog.CatalogBuilder.buildCoverage(CatalogBuilder.java:900) at org.geoserver.web.data.layer.NewLayerPage.buildLayerInfo(NewLayerPage.java:410) ... 122 more This most often happens when first loading the layer into GeoServer, but I've also encountered it when trying to view any time dimension other then the first.
[Geoserver-devel] [JIRA] (GEOS-9345) Associate roles to security groups via REST
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-9345 Associate roles to security groups via REST Issue Type: Improvement Assignee: Unassigned Components: REST, Security Created: 24/Sep/19 11:21 PM Priority: Medium Reporter: Torben Barsballe When the Security REST API was expanded for GeoServer 2.12, the ability to add (and remove) roles to users was included, but not the ability to add roles to groups. An endpoint to add roles to groups should be added to match the existing endpoint for users. Add Comment
[Geoserver-devel] [JIRA] (GEOS-9311) Switching from System Status to Modules tab gives an error.
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-9311 Switching from System Status to Modules tab gives an error. Issue Type: Bug Affects Versions: 2.16-RC Assignee: Unassigned Created: 28/Aug/19 1:33 AM Priority: Medium Reporter: Torben Barsballe Steps to Reproduce: 1. (Re)start GeoServer 2. Navigate to localhost:8080/geoserver/web and login 3. Navigate to the Server Status page. 4. Click the System Status tab 5. Click the Modules tab. This will give an error (below). The error sometimes does not occur if you have already viewed the Module tab during the current GeoServer session. Error message: org.apache.wicket.behavior.InvalidBehaviorIdException: Cannot find behavior with id '0' on component 'org.geoserver.web.admin.ModuleStatusPanel:tabs:panel' in page '[Page class = org.geoserver.web.admin.StatusPage, id = 4, render count = 1]'. Perhaps the behavior did not properly implement getStatelessHint() and returned 'true' to indicate that it is stateless instead of returning 'false' to indicate that it is stateful. at org.apache.wicket.Behaviors.getBehaviorById(Behaviors.java:316) at org.apache.wicket.Component.getBehaviorById(Component.java:4596) at org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.invokeListener(ListenerInterfaceRequestHandler.java:247) 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
[Geoserver-devel] [JIRA] (GEOS-9228) Renaming a layer doesn't update Data Security rules
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-9228 Renaming a layer doesn't update Data Security rules Issue Type: Bug Assignee: Unassigned Created: 23/May/19 8:06 PM Priority: Medium Reporter: Torben Barsballe If you create a Data Security rule which references a layer, and then later rename the layer, the Data Security rule does not get updated with the new layer name, causing the security of the renamed layer to change. Add Comment Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS
[Geoserver-devel] [JIRA] (GEOS-9213) GeoFence should support adding security rules for layer groups
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-9213 GeoFence should support adding security rules for layer groups Issue Type: New Feature Assignee: Unassigned Components: GeoFence Created: 13/May/19 8:39 PM Priority: Medium Reporter: Torben Barsballe GeoServer supports adding security configurations for Layer Groups. GeoFence does not. As GeoFence is intended to be a complete replacement for GeoServers authorization system, GeoFence should support adding security rules for layer groups. Add Comment
[Geoserver-devel] [JIRA] (GEOS-9212) GeoFence Internal Server plugin gives NPE when run from web/app
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-9212 GeoFence Internal Server plugin gives NPE when run from web/app Issue Type: Bug Assignee: Unassigned Components: GeoFence Created: 13/May/19 7:48 PM Priority: Medium Reporter: Torben Barsballe The geofence-server profile does not work properly when running from the demo web app - the beans in geofence-services-impl-3.4.2.jar/applicationContext.xml do not get loaded at startup, leading to NPEs on all of the GeoFence admin pages. For example: ... Caused by: java.lang.NullPointerException at org.hibernate.impl.SessionFactoryImpl.getClassMetadata(SessionFactoryImpl.java:807) at com.googlecode.genericdao.search.hibernate.HibernateMetadataUtil.get(HibernateMetadataUtil.java:92) at com.googlecode.genericdao.dao.jpa.JPABaseDAO._all(JPABaseDAO.java:206) at com.googlecode.genericdao.dao.jpa.GenericDAOImpl.findAll(GenericDAOImpl.java:61) at org.geoserver.geofence.core.dao.impl.RuleDAOImpl.findAll(RuleDAOImpl.java:101) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:343) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163) at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:294) at
[Geoserver-devel] [JIRA] (GEOS-9049) Disable spatialite community module pending GeoTools support
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-9049 Disable spatialite community module pending GeoTools support Issue Type: Bug Assignee: Unassigned Created: 07/Dec/18 11:37 PM Priority: Medium Reporter: Torben Barsballe gt-jdbc-spatialite is currently disabled pending Java 11 support. The corresponding community module should likewise be removed from the release profile until geotools support is re-established Add Comment Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS This message was
[Geoserver-devel] [JIRA] (GEOS-9044) Can't modify existing GWC blobstore via UI without renaming
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-9044 Can't modify existing GWC blobstore via UI without renaming Issue Type: Bug Assignee: Unassigned Attachments: modify_blobstore.png Components: GWC, Wicket UI Created: 30/Nov/18 8:31 PM Priority: Medium Reporter: Torben Barsballe Create a FileBlobStore using the Wicket UI and save it. Open the same blob store for editing. Make a change other than the name and save it. Produces error "This identifier is already in use, please choose a unique one." Add Comment
[Geoserver-devel] [JIRA] (GEOS-8916) Update Xalan serializer to 2.7.2
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8916 Update Xalan serializer to 2.7.2 Issue Type: Task Assignee: Unassigned Created: 05/Sep/18 1:29 AM Priority: Medium Reporter: Torben Barsballe Add Comment Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100091-sha1:0a6ef10) -- Check
[Geoserver-devel] [JIRA] (GEOS-8905) Cannot add CSV Store
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8905 Cannot add CSV Store Issue Type: Bug Affects Versions: 2.13.2 Assignee: Unassigned Created: 24/Aug/18 9:27 PM Priority: Medium Reporter: Torben Barsballe When trying to add a CSV store, I get the following error when publishing the layer: [wicket portion ommited] ... Caused by: java.lang.RuntimeException: Error occurred while building the resources for the configuration page at org.geoserver.web.data.layer.NewLayerPage.buildLayerInfo(NewLayerPage.java:435) at org.geoserver.web.data.layer.NewLayerPage$9.onClick(NewLayerPage.java:324) at org.geoserver.web.wicket.SimpleAjaxLink$1.onClick(SimpleAjaxLink.java:47) at org.apache.wicket.ajax.markup.html.AjaxLink$1.onEvent(AjaxLink.java:85) at org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:155) at org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:601) ... 105 more Caused by: java.lang.RuntimeException: Failure reading csv file at org.geotools.data.csv.parse.CSVStrategy.createBuilder(CSVStrategy.java:80) at org.geotools.data.csv.parse.CSVAttributesOnlyStrategy.buildFeatureType(CSVAttributesOnlyStrategy.java:43) at org.geotools.data.csv.parse.CSVStrategy.getFeatureType(CSVStrategy.java:59) at org.geotools.data.csv.CSVDataStore.getSchema(CSVDataStore.java:77) at org.geotools.data.csv.CSVFeatureSource.buildFeatureType(CSVFeatureSource.java:94) at org.geotools.data.store.ContentFeatureSource.getAbsoluteSchema(ContentFeatureSource.java:328) at org.geotools.data.store.ContentFeatureSource.getSchema(ContentFeatureSource.java:297) at org.geotools.data.store.ContentFeatureSource.getSchema(ContentFeatureSource.java:106) at org.geoserver.catalog.CatalogBuilder.buildFeatureType(CatalogBuilder.java:343)
[Geoserver-devel] [JIRA] (GEOS-8895) "Chunk [] is not a valid entry" error for the embedded GWC reload endpoint
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8895 "Chunk [] is not a valid entry" error for the embedded GWC reload endpoint Issue Type: Bug Assignee: Unassigned Created: 15/Aug/18 6:07 PM Priority: Medium Reporter: Torben Barsballe POSTing to http://localhost:8080/geoserver/gwc/rest/reload or clicking the Reload TileLayerConfiguration button on the http://localhost:8080/geoserver/gwc/demo page gives the following error: 2018-08-15 09:23:15,161 ERROR [geoserver.rest] - Chunk [] is not a valid entry java.lang.IllegalArgumentException: Chunk [] is not a valid entry at com.google.common.base.Preconditions.checkArgument(Preconditions.java:148) at com.google.common.base.Splitter$MapSplitter.split(Splitter.java:508) at org.geowebcache.rest.controller.ReloadController.splitToMap(ReloadController.java:128) at org.geowebcache.rest.controller.ReloadController.doPost(ReloadController.java:77) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:205) at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:133) at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:116) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:827) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:738) at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85) at
[Geoserver-devel] [JIRA] (GEOS-8869) Cannot set default style using layer PUT
Title: Message Title
Torben Barsballe created an issue
GeoServer / GEOS-8869
Cannot set default style using layer PUT
Issue Type:
Bug
Assignee:
Unassigned
Created:
01/Aug/18 9:19 PM
Priority:
Medium
Reporter:
Torben Barsballe
When doing a PUT to localhost:8080/geoserver/rest/layers/tiger:poi with the contents {"layer":{"name":"poi","defaultStyle":{"name":"capitals"}}}, the defaultStyle does not get updated. This only affects JSON PUT, XML works fine. This also only occurs when the Importer extension is installed. The issue appears to be being caused because ImportLayerJSONMessageConverter is being used instead of XStreamJSONMessageConverter. The constraints on the Importer converter need to be tightened.
Add Comment
[Geoserver-devel] [JIRA] (GEOS-8806) Catalog security does not prevent styles from being edited via REST
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8806 Catalog security does not prevent styles from being edited via REST Issue Type: Bug Assignee: Unassigned Components: REST, Security, styling Created: 28/Jun/18 8:52 PM Priority: Medium Reporter: Torben Barsballe The order of options involved in saving a style (via rest) can cause issues under certain auth patterns. Example: Prerequisites: -Have 2 workspaces, ws1 and ws2 -Have 2 users, foo, with readwrite access to ws1 but not ws2; and bar, with readwrite access to ws2 but not ws1 -Have the REST /workspaces/*/styles endpoint accessible by ROLE_AUTHENTICATED Steps to reproduce: foo tries to edit a style in ws2 via REST Result: A 500 error will be returned, but the contents of the style will still be changed. The problem can be seen here: https://github.com/geoserver/geoserver/blob/2.13.0/src/restconfig/src/main/java/org/geoserver/rest/catalog/StyleController.java#L395 The contents of the style resource get changed before the style gets saved to the catalog. Since the Resource store doesn't have any security, this just happens. Then the StyleInfo is saved to the catalog, and there is failure due to security. However, the change has already been made to the resource, and doesn't get reverted. There seem to be a few options for fixing this. The most robust would be to have catalog security rules apply to the appropriate objects in the Resource store. This would almost certainly be a substantial api change, and worthy of a GSIP. The simple solution would just be to attempt a save of the unmodified style immediately after receiving the request.
[Geoserver-devel] [JIRA] (GEOS-8800) GWC Enable Data Security can't be clicked on
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8800 GWC Enable Data Security can't be clicked on Issue Type: Bug Assignee: Unassigned Attachments: gwc_data_security.png Components: GWC Created: 22/Jun/18 9:46 PM Priority: Medium Reporter: Torben Barsballe The GWC Enable Data Security Checkbox is hidden by the margin of the next heading, and can't be (easily) clicked on. Add Comment
[Geoserver-devel] [JIRA] (GEOS-8746) Fullscreen Style Editor
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8746 Fullscreen Style Editor Issue Type: Improvement Assignee: Unassigned Components: styling Created: 15/May/18 7:07 PM Priority: Medium Reporter: Torben Barsballe Add Comment Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085-sha1:5dcb565)
[Geoserver-devel] [JIRA] (GEOS-8607) DataAccessRuleDao logging skips workspaced layergroups
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8607 DataAccessRuleDao logging skips workspaced layergroups Issue Type: Bug Assignee: Unassigned Created: 28/Feb/18 6:09 PM Priority: Low Reporter: Torben Barsballe When parsing security rules, class DataAccessRuleDao log a warn when a rule doesn't match an existing layer. This check doesn't handle layergroups in workspaces, only workspaces, layers with or without workspaces and layergroups without workspace. Add Comment Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS
[Geoserver-devel] [JIRA] (GEOS-8595) PDF Docs show 2.12-SNAPSHOT instead of correct version
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8595 PDF Docs show 2.12-SNAPSHOT instead of correct version Issue Type: Bug Affects Versions: 2.12.2, 2.13-beta Assignee: Unassigned Created: 21/Feb/18 7:26 PM Priority: Medium Reporter: Torben Barsballe The GeoServer PDF Docs show 2.12-SNAPSHOT instead of the correct version. This affects all branches 2.12.x and higher - the 2.11.5 build shows the correct version: https://build.geoserver.org/geoserver/release/2.11.5/geoserver-2.11.5-user-manual.pdf https://build.geoserver.org/geoserver/release/2.12.2/geoserver-2.12.2-user-manual.pdf https://build.geoserver.org/geoserver/release/2.13-beta/geoserver-2.13-beta-user-manual.pdf The contents of the docs still appear to be correct; I can find the new NSG Profile community modules in the 2.13-beta docs but not the 2.12.2 docs. Add Comment
[Geoserver-devel] [JIRA] (GEOS-8544) Demo Page does not send password
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8544 Demo Page does not send password Issue Type: Bug Assignee: Unassigned Created: 22/Jan/18 8:33 PM Priority: Medium Reporter: Torben Barsballe As of 2.11-RC1, the demo page is no longer sending the password, with the request, such that authenticated requests do not work. This appears to have been caused by updating to Wicket 7.6. See WICKET-6211 Add Comment Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS This message was sent by Atlassian
[Geoserver-devel] [JIRA] (GEOS-8543) Demo request page - invalid error response
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8543 Demo request page - invalid error response Issue Type: Bug Assignee: Unassigned Created: 22/Jan/18 8:31 PM Priority: Medium Reporter: Torben Barsballe When Data or Service security limits are set such that the Unauthenticated user cannot view the results of a request, there is an error in the error response: XML Parsing Error: XML or text declaration not at start of entity Location: http://localhost:8080/geoserver/TestWfsPost Line Number 3, Column 1: ^ Using developer tools network tab shows the following: java.lang.NullPointerException It appears that the beginning section of the XML response is duplicated Add Comment
[Geoserver-devel] [JIRA] (GEOS-8536) SRS Description Page overwrites HeaderContributions
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8536 SRS Description Page overwrites HeaderContributions Issue Type: Bug Assignee: Unassigned Created: 18/Jan/18 12:25 AM Priority: Medium Reporter: Torben Barsballe The SRS Description Page ignores all HeaderContributions configured in applicationContext files, because it overrides the renderHead method of GeoServerBasePage and doesn't invoke super. Add Comment Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS This message was sent by Atlassian
[Geoserver-devel] [JIRA] (GEOS-8460) Importer doesn't pass spring request context to context creation thread (when in async mode)
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8460 Importer doesn't pass spring request context to context creation thread (when in async mode) Issue Type: Bug Assignee: Unassigned Components: GeoFence, Importer Created: 01/Dec/17 11:01 PM Priority: Medium Reporter: Torben Barsballe Similar to GEOS-7676 Closed , when performing an asynchronous import, GeoServer doesn't pass the spring context onto the importer initialization thread. This can cause a security error if you are using GeoFence and importing into an existing store, as the store to be imported into will be resolved without authentication, usually resulting in it being limited to READ_ONLY. Add Comment
[Geoserver-devel] [JIRA] (GEOS-8418) Multipart Requests fail when using gs-geogig
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8418 Multipart Requests fail when using gs-geogig Issue Type: Bug Assignee: Unassigned Created: 22/Nov/17 10:52 PM Priority: Medium Reporter: Torben Barsballe When using the gs-geogig plugin, multipart requests will fail. This includes all form requests from Wicket, such as creating a new style. For example: org.apache.wicket.WicketRuntimeException: Method onRequest of interface org.apache.wicket.behavior.IBehaviorListener targeted at org.apache.wicket.ajax.markup.html.form.AjaxSubmitLink$1@24b8ce4c on component [ConfirmOverwriteSubmitLink [Component id = copy]] threw an exception at org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:268) 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:661) at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) at
[Geoserver-devel] [JIRA] (GEOS-8401) Embeded GWC Rest Seeding fails with CannotResolveClassException
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8401 Embeded GWC Rest Seeding fails with CannotResolveClassException Issue Type: Bug Affects Versions: 2.12.0 Assignee: Unassigned Components: GWC Created: 18/Nov/17 1:48 AM Priority: Medium Reporter: Torben Barsballe Performing a REST seed request results in com.thoughtworks.xstream.mapper.CannotResolveClassException: seedRequest This appears to be limited to embedded GeoWebCache (standalone works fine, I think), and looks to be caused by interference from the default GeoServer XML converter. Add Comment
[Geoserver-devel] [JIRA] (GEOS-8390) PUTing a MBStyle without raw=true returns 200 OK but results in an empty style body.
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8390 PUTing a MBStyle without raw=true returns 200 OK but results in an empty style body. Issue Type: Bug Assignee: Unassigned Created: 13/Nov/17 10:20 PM Priority: Medium Reporter: Torben Barsballe If I try to PUT an MBStyle body to an existing style, I get a 200 OK response but the style body in GeoServer is empty (viewing via the UI, REST API, or REST resource endpoint). If I add the `?raw=true` parameter to my request, the style body has the correct contents. GeoServer should return an error in the first case. Add Comment Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS
[Geoserver-devel] [JIRA] (GEOS-8380) MBstyle - fill-outline-color should be disabled by fill-pattern
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8380 MBstyle - fill-outline-color should be disabled by fill-pattern Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2017-11-07 at 2.24.35 PM.png Created: 07/Nov/17 11:28 PM Priority: Medium Reporter: Torben Barsballe From the MapBox Style spec: fill-outline-color Paint property. Optional color. Disabled by fill-pattern. Requires fill-antialias to be . Supports all curve types. Transitionable. The outline color of the fill. Matches the value of fill-color if unspecified. When rendering a style with a fill pattern in geoserver, the outline should therefore be disabled. However, it is not: Add Comment
[Geoserver-devel] [JIRA] (GEOS-8348) MBStyle - Add label priority based on layer order
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8348 MBStyle - Add label priority based on layer order Issue Type: Bug Assignee: Unassigned Created: 17/Oct/17 1:11 AM Priority: Medium Reporter: Torben Barsballe Based on the discussion here , label order defines priority in mabox style. This behavior should be added to the geoserver implementation (by adding the appropriate vendor options when converting to SLD). Add Comment Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS This message was
[Geoserver-devel] [JIRA] (GEOS-8347) MBStyle should create single NamedLayer when possible
Title: Message Title
Torben Barsballe created an issue
GeoServer / GEOS-8347
MBStyle should create single NamedLayer when possible
Issue Type:
Bug
Assignee:
Unassigned
Created:
16/Oct/17 11:08 PM
Priority:
Medium
Reporter:
Torben Barsballe
When an MBStyle is converted to SLD, it should create a single NamedLayer wherever possible. MBStyle supports different source-layer}}s for each styled {{layer in the MBStyle. To support this in SLD, each layer is converted into its own NamedLayer, referencing the source-layer. Whenever there is a block of layer elements with the same source-layer in an mbstyle, they should be merged as separate FeatureTypeStyles within a single NamedLayer. Order must still be preserved, so two layer}}s with the same {{source-layer that are separated by a layer with a different source-layer should not be merged.
Add Comment
[Geoserver-devel] [JIRA] (GEOS-8346) MBStyle line-gap produces strange results
Title: Message Title
Torben Barsballe created an issue
GeoServer / GEOS-8346
MBStyle line-gap produces strange results
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
Screen Shot 2017-10-16 at 9.49.43 AM.png
Created:
16/Oct/17 7:05 PM
Priority:
Medium
Reporter:
Torben Barsballe
The line-gap property for MBStyle produces unexpected results. MBStyle:
"type": "line",
"paint": {
"line-color": "#FFCC00",
"line-width": 4,
"line-cap": "round"
}
Generated SLD:
mitre
8
4
0
#FF
mitre
8
4
1
0
mitre
8
0
This produces: A black stroke of width 12, a white stroke of width 11, and a black stroke of width 8. What I would expect - Either:
Two black strokes (width 8), one with a perpendicularOffset of -6, the other with a perpendicularOffset of 6 (6 = 1/2 (width + gap) = 8+4 / 2).
One black stroke of width 20, one white stroke of width 4 (only as a workaround if the former doesn't work)
Resulting visuals attached (There is some other styling on that screenshot, only the big black line is the issue here)
[Geoserver-devel] [JIRA] (GEOS-8343) MBStyle error with zoom-and-property function
Title: Message Title
Torben Barsballe created an issue
GeoServer / GEOS-8343
MBStyle error with zoom-and-property function
Issue Type:
Bug
Assignee:
Unassigned
Created:
13/Oct/17 11:30 PM
Priority:
Medium
Reporter:
Torben Barsballe
The following style:
{
"version": 8,
"name": "places",
"layers": [
{
"id": "places-circle",
"source-layer": "ne_50m_populated_places",
"minzoom": 2,
"filter": ["!=", "ADM0CAP", 1],
"type": "circle",
"paint": {
"circle-color": "#33",
"circle-radius": {
"property": "POP_MAX",
"type": "exponential",
"stops": [
[{"zoom": 0, "value": 0}, 3],
[{"zoom": 0, "value": 4000}, 3]
[{"zoom": 3, "value": 0}, 3],
[{"zoom": 3, "value": 4000}, 5]
]
}
}
}
]
}
Produces an {IllegalStateException: Layer places-circle:Reduce zoom and property function prior to use.} Looks like some part of the circle layer conversion is not calling reduce before converting the function
[Geoserver-devel] [JIRA] (GEOS-8324) StackOverflow exception when comparing FeatureTypeInfo
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8324 StackOverflow exception when comparing FeatureTypeInfo Issue Type: Bug Assignee: Unassigned Created: 06/Oct/17 11:53 PM Priority: Medium Reporter: Torben Barsballe Using .equals() with FeatureTypeInfoImpls which contain a non-empty list of AttributeTypeInfoImpls and are equal, but not the same object, will result in a StackOverflowException. So far, I have not been able to reproduce this in any runtime code, just in test cases (I expect we don't actually use FeatureTypeInfoImpl.equals anywhere that this could crop up). Add Comment Get JIRA notifications on your phone! Download the JIRA Cloud app for Android or iOS
[Geoserver-devel] [JIRA] (GEOS-8308) GeoWebCache Rest endpoints showing up truncated in rest index
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8308 GeoWebCache Rest endpoints showing up truncated in rest index Issue Type: Bug Affects Versions: 2.12-beta, 2.12-RC1 Assignee: Torben Barsballe Components: REST Created: 29/Sep/17 12:52 AM Priority: Medium Reporter: Torben Barsballe When visiting the /geoserver/rest index page, the GWC end-points seem to be indexed and prefixed with EST: est est/diskquota est/layers est/masstruncate est/seed.json est/statistics Attempting to visit these links gives a 404. Add Comment
[Geoserver-devel] [JIRA] (GEOS-8300) REST GET resource metadata - file extension can override format parameter
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8300 REST GET resource metadata - file extension can override format parameter Issue Type: Bug Affects Versions: 2.12-beta Assignee: Unassigned Components: REST Created: 25/Sep/17 11:42 PM Priority: Medium Reporter: Torben Barsballe If you make a REST GET request for resource metadata against a resource with a filename that includes an extension that is among the supported configuration formats (xml, html, json), then the filename of the resource will determine the content of the response rather than the format parameter. For example, the request: http://localhost:8080/geoserver/rest/resource/styles/point.xml?operation=METADATA=json Will return metadata about the resource point.xml in XML format with content-type=application/json However, the request http://localhost:8080/geoserver/rest/resource/styles/point.sld?operation=METADATA=json Will return metadata about the resource point.sld in JSON format, since sld is not a configuration format.
[Geoserver-devel] [JIRA] (GEOS-8297) REST templates endpoint uses PUT to create new templates.
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8297 REST templates endpoint uses PUT to create new templates. Issue Type: Bug Assignee: Unassigned Components: REST Created: 23/Sep/17 1:43 AM Priority: Medium Reporter: Torben Barsballe The templates endpoints use PUT to create new templates, when they should use POST. This affects both the pre-REST-API Refresh restlet API and the new Spring MVC API. Since this has been the case long enough that I am sure people rely on it, we can't really remove this functionality. However, we can add a proper POST endpoint to be a bit more REST-compliant. Add Comment
[Geoserver-devel] [JIRA] (GEOS-8296) Add purge paramater to REST datastores DELETE
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8296 Add purge paramater to REST datastores DELETE Issue Type: Improvement Assignee: Unassigned Components: REST Created: 22/Sep/17 10:10 PM Priority: Medium Reporter: Torben Barsballe The coveragestore DELETE endpoint has a purge parameter, which is used to delete the underlying files in addition to the store. This may be useful to add to the datastores DELETE endpoint as well, either to delete the underlying file (in the case of a shapefile) or table (in the case of a database). In the case of databases, this parameter may also be useful for featuretype DELETE, to delete individual tables when a featuretype is removed. Add Comment
[Geoserver-devel] [JIRA] (GEOS-8294) REST GET style does not support pretty print
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8294 REST GET style does not support pretty print Issue Type: Bug Affects Versions: 2.12-beta Assignee: Unassigned Created: 20/Sep/17 1:57 AM Priority: Medium Reporter: Torben Barsballe After the REST API Refresh, GET style does not support the pretty print option. This is a regression from 2.11.x, and appears to have come about due to the separation between Controllers and Converters. Add Comment Get JIRA notifications
[Geoserver-devel] [JIRA] (GEOS-8293) REST /layers/{layer}/styles entries do not redirect to the correct URL.
Title: Message Title
Torben Barsballe created an issue
GeoServer / GEOS-8293
REST /layers/{layer}/styles entries do not redirect to the correct URL.
Issue Type:
Bug
Affects Versions:
2.12-beta
Assignee:
Unassigned
Created:
20/Sep/17 1:07 AM
Priority:
Medium
Reporter:
Torben Barsballe
When querying /layers/{layer}/styles, a list of styles for that layer is returned, with links to the REST locations of those styles. Trying to visit any of those links returns a 404. These should be updated to link to the correct styles, under /styles/{style} or /workspaces/{workspace}/styles/{style}. Note that the pre-REST-API refresh REST API does support GETing styles from /layers/{layer}/styles/{style}, however this seems to be simply a happy accident, as that endpoint is not registered in the application context, and /layers/{layer}/styles/{style} behaves exactly the same as /layers/{layer}/styles/foo/bar{style} (note the foo/bar). If we wanted to retain this functionality, we should still update the links, and merely retain the /layers/{layer}/styles/{style} for legacy compatibility.
Add Comment
[Geoserver-devel] [JIRA] (GEOS-8292) REST API Swagger docs
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8292 REST API Swagger docs Issue Type: Story Assignee: Torben Barsballe Created: 19/Sep/17 11:05 PM Priority: Medium Reporter: Torben Barsballe The REST API Swagger docs are still not 100% complete, and need some improvements. Add Comment Get JIRA notifications on your phone! Download the JIRA Cloud app for Android or iOS This message was sent by Atlassian Jira (v1000.1299.0#100060-sha1:8cb2c24)
[Geoserver-devel] [JIRA] (GEOS-8291) "generic" style configuration not linking to correct sld
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8291 "generic" style configuration not linking to correct sld Issue Type: Bug Assignee: Unassigned Created: 19/Sep/17 5:48 PM Priority: Medium Reporter: Torben Barsballe When loading the styles, get the following exception: java.io.IOException: No such resource: generic.sld Looks like the "generic" style is referencing the file "generic.sld" when it should be pointing to "default_generic.sld" Add Comment Get JIRA notifications on your phone! Download the JIRA Cloud app for Android or iOS
[Geoserver-devel] [JIRA] (GEOS-8289) AbstractCatalogFacade.resolve(StyleInfo) does not resolve the workspace
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8289 AbstractCatalogFacade.resolve(StyleInfo) does not resolve the workspace Issue Type: Bug Assignee: Unassigned Created: 15/Sep/17 1:47 AM Priority: Medium Reporter: Torben Barsballe AbstractCatalogFacade.resolve(StyleInfo) does not resolve the workspace, unlike other similar resolve() methods, such as Store. This was likely missed because style workspaces are optional, and are not widely used. Add Comment Get JIRA notifications on your phone! Download the JIRA Cloud app for Android or iOS
[Geoserver-devel] [JIRA] (GEOS-8245) Style Based Layer Groups
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8245 Style Based Layer Groups Issue Type: New Feature Assignee: Torben Barsballe Created: 03/Aug/17 12:02 AM Priority: Medium Reporter: Torben Barsballe See: https://github.com/geoserver/geoserver/wiki/GSIP-161 Add Comment Get JIRA notifications on your phone! Download the JIRA Cloud app for Android or iOS This message was sent by Atlassian JIRA (v1000.1154.0#100057-sha1:fec937e)
[Geoserver-devel] [JIRA] (GEOS-8238) REST API root resources HTML endpoint gives error
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8238 REST API root resources HTML endpoint gives error Issue Type: Bug Assignee: Unassigned Created: 29/Jul/17 12:20 AM Priority: Medium Reporter: Torben Barsballe If you visit "localhost:8080/geoserver/rest/resource" in a browser, or with format=html, you get the following error: Resource Directory ' _expression_ properties.parent.path is undefined on line 10, column 27 in resourceDirectoryInfo.ftl Add Comment
[Geoserver-devel] [JIRA] (GEOS-8226) REST - GET wmslayers by store returns results from the default workspace
Title: Message Title
Torben Barsballe created an issue
GeoServer / GEOS-8226
REST - GET wmslayers by store returns results from the default workspace
Issue Type:
Bug
Affects Versions:
2.11.1
Assignee:
Torben Barsballe
Components:
REST
Created:
18/Jul/17 6:19 PM
Priority:
Medium
Reporter:
Torben Barsballe
All queries to the REST geoserver/rest/workspaces/{workspace}/wmsstores/{wmsstore}/wmslayers endpoint return results in the default workspace if such a store exists there. This means that if you have a store in the default workspace and a different store with the same name in another workspace, querying for layers in the second store will actually return layers from the first store. Steps to reproduce: Assume ws1 is the default workspace and ws2 is some other workspace. Create a cascaded WMS store named foo in ws1 and a different cascaded wms store in ws2 with the same name. Query localhost:8080/geoserver/rest/workspaces/ws2/wmsstores/foo/wmslayers. The result will list the layers from the store in ws1 instead of the store in ws2.
[Geoserver-devel] [JIRA] (GEOS-8221) GeoServerDataDir returns the root directory if workspace is null
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8221 GeoServerDataDir returns the root directory if workspace is null Issue Type: Bug Assignee: Unassigned Created: 12/Jul/17 6:25 PM Priority: Medium Reporter: Torben Barsballe The GeoServerDataDirectory class has a number of "get__()" methods with a workspace version and a no workspace (global) version.For example: getStyles() . Typically, in the catalog if a null workspace is provided, the global 'workspace' is assumed. However, if you provide a null workspace to one of these methods, you get back the root of the data dir, instead of whatever you were asking for. This behaviour seems contrary to how most of the rest of GeoServer works, and rather error prone. These methods should be changed to handle the case of a null workspace as if it were the global "workspace". Add Comment
[Geoserver-devel] [JIRA] (GEOS-8186) build.geoserver.org - Add an artifact server for releases
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8186 build.geoserver.org - Add an artifact server for releases Issue Type: Sub-task Assignee: Unassigned Created: 13/Jun/17 9:53 PM Priority: Medium Reporter: Torben Barsballe See http://ares.boundlessgeo.com/geotools/ and http://ares.boundlessgeo.com/geoserver/ for examples how this was implemented in ares. I believe it is just a simple apache file server with a bunch of different endpoints exposed (geotools, geoserver, and others) Add Comment This message was sent by Atlassian JIRA (v1000.1045.2#100046-sha1:c375a71)
[Geoserver-devel] [JIRA] (GEOS-8185) build.geoserver.org - set up cite tests
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8185 build.geoserver.org - set up cite tests Issue Type: Sub-task Assignee: Unassigned Created: 13/Jun/17 9:51 PM Priority: Medium Reporter: Torben Barsballe Add Comment This message was sent by Atlassian JIRA (v1000.1045.2#100046-sha1:c375a71) -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org!
[Geoserver-devel] [JIRA] (GEOS-8184) Bring build.geoserver.org up to full functionality
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8184 Bring build.geoserver.org up to full functionality Issue Type: Task Assignee: Unassigned Created: 13/Jun/17 9:39 PM Priority: Medium Reporter: Torben Barsballe ares is being replaced by a new community build server, build.geoserver.org. The Jenkins server is in place, but there are still some things that need to be added before this matches the functionality of ares. Add Comment This message was sent by Atlassian JIRA (v1000.1045.2#100046-sha1:c375a71)
[Geoserver-devel] [JIRA] (GEOS-8183) Remove VPF Documentation
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8183 Remove VPF Documentation Issue Type: Task Assignee: Torben Barsballe Created: 12/Jun/17 10:12 PM Priority: Medium Reporter: Torben Barsballe The VPF (Vector Product Format) extension was removed in GeoServer 2.5, but documentation for is is still included in the user manual. This documentation should be removed so as to not cause confusion. Add Comment This message was sent by Atlassian JIRA (v1000.1043.2#100046-sha1:a1d8ef5)
[Geoserver-devel] [JIRA] (GEOS-8164) java.util.HashMap cannot be cast to org.eclipse.emf.ecore.EObject when sending WCS XML GetCoverage request
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8164 java.util.HashMap cannot be cast to org.eclipse.emf.ecore.EObject when sending WCS XML GetCoverage request Issue Type: Bug Assignee: Unassigned Components: WCS Created: 31/May/17 1:04 AM Priority: Medium Reporter: Torben Barsballe Given an arbitrary coverage, run: noformat curl -v -u admin:geoserver -XPOST -H "Content-type: text/xml" -d @getcov2.xml "localhost:8080/geoserver/wcs" noformat See getcov2.xml, attached, and change the "topp__world" to your exact coverage id. NOTE: REQUEST COULD BE WRONG, got from http://mapserver.org/ogc/wcs_server.html#wcs-2-0 GeoServer returns the following error message: java.lang.ClassCastException: java.util.HashMap cannot be cast to org.eclipse.emf.ecore.EObject java.util.HashMap cannot be cast to org.eclipse.emf.ecore.EObject [] The full stacktrace from the logs is: java.lang.ClassCastException: java.util.HashMap cannot be cast to org.eclipse.emf.ecore.EObject at net.opengis.wcs20.impl.ExtensionItemTypeImpl.getObjectContent(ExtensionItemTypeImpl.java:194) at net.opengis.wcs20.impl.ExtensionItemTypeImpl.eGet(ExtensionItemTypeImpl.java:241) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eGet(BasicEObjectImpl.java:1021) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eGet(BasicEObjectImpl.java:1013) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eGet(BasicEObjectImpl.java:1008) at org.geoserver.ows.util.EMFLogger.log(EMFLogger.java:37) at
[Geoserver-devel] [JIRA] (GEOS-8163) Duplicate GeoPackage formats in layer preview page
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8163 Duplicate GeoPackage formats in layer preview page Issue Type: Bug Assignee: Unassigned Components: geopackage Created: 30/May/17 11:57 PM Priority: Low Reporter: Torben Barsballe With the GeoPackage extension installed, there are four slightly different GeoPackage formats listed under the WFS formats section of the Layer Preview Page "Choose format" dropdown. All four use the same output format and have the same effect. See attached screenshot for an example. Add Comment
[Geoserver-devel] [JIRA] (GEOS-8162) CSV Data store does not support relative store paths
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8162 CSV Data store does not support relative store paths Issue Type: Bug Assignee: Unassigned Created: 30/May/17 10:28 PM Priority: Medium Reporter: Torben Barsballe When trying to publish a layer from a csv store, I get the following error: java.lang.RuntimeException: Error occurred while building the resources for the configuration page at org.geoserver.web.data.layer.NewLayerPage.buildLayerInfo(NewLayerPage.java:356) at org.geoserver.web.data.layer.NewLayerPage$8.onClick(NewLayerPage.java:281) at org.geoserver.web.wicket.SimpleAjaxLink$1.onClick(SimpleAjaxLink.java:46) at org.apache.wicket.ajax.markup.html.AjaxLink$1.onEvent(AjaxLink.java:68) at org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:177) at org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:300) at org.apache.wicket.request.target.component.listener.BehaviorRequestTarget.processEvents(BehaviorRequestTarget.java:119) at org.apache.wicket.request.AbstractRequestCycleProcessor.processEvents(AbstractRequestCycleProcessor.java:92) at org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1250) at org.apache.wicket.RequestCycle.step(RequestCycle.java:1329) at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1436) at org.apache.wicket.RequestCycle.request(RequestCycle.java:545) at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:484) at org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:138) at javax.servlet.http.HttpServlet.service(HttpServlet.java:620) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at org.springframework.web.servlet.mvc.ServletWrappingController.handleRequestInternal(ServletWrappingController.java:156) at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153) at
[Geoserver-devel] [JIRA] (GEOS-8161) GeoServer Importer does not support Geometries in CSV Stores
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8161 GeoServer Importer does not support Geometries in CSV Stores Issue Type: Bug Assignee: Unassigned Components: Importer Created: 30/May/17 10:25 PM Priority: Lowest Reporter: Torben Barsballe The GeoServer importer is currently only able to import CSV's as lists of attributes only (no Geometry). Given that Geometry support does exist in the CSV DataStore, importer should probably support it. Add Comment This message
[Geoserver-devel] [JIRA] (GEOS-8160) Importer - strange default postgis database name on windows
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8160 Importer - strange default postgis database name on windows Issue Type: Bug Assignee: Unassigned Components: Importer Created: 30/May/17 10:21 PM Priority: Lowest Reporter: Torben Barsballe When adding data from a PostGIS store using the Importer, the default database/username is usually populated from current user. Using a Windows 7 VM, it is instead filled with OG7VM2011$. This does not seem especially user-friendly. (Note: this appears to be the computer name, followed by a $) Add Comment
[Geoserver-devel] [JIRA] (GEOS-8155) Cannot delete style in a workspace if it has the name of a default style
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8155 Cannot delete style in a workspace if it has the name of a default style Issue Type: Bug Assignee: Unassigned Components: web Created: 26/May/17 10:51 PM Priority: Medium Reporter: Torben Barsballe If you try and delete a workspaced style that has the same name as one of the default styles (point, line, polygon, raster, generic), you get an error message in the UI. This should not be the case - only global default styles should be undeleteable. Add Comment
[Geoserver-devel] [JIRA] (GEOS-8144) Table of contents background is broken if larger than 800px high
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8144 Table of contents background is broken if larger than 800px high Issue Type: Bug Assignee: Unassigned Components: Documentation Created: 18/May/17 12:17 AM Priority: Medium Reporter: Torben Barsballe The background-image used for the Table of Contents sidebar in the GeoServer doc style is a 800px high image. When the table of contents is less than 800px high, the background image is truncated, and displays normally. When the table of contents is larger than 800px high, there is a gap between this background image and the top of the table of contents. Examples: http://docs.geoserver.org/latest/en/user/tutorials/imagemosaic_timeseries/imagemosaic_timeseries.html http://docs.geoserver.org/latest/en/user/styling/mbstyle/reference/spec.html There are a couple routes to fixing this: a) Add a tileable segment, to be inserted when the TOC is larger than 800 px. b) Instead of using a background image, we can just use a CSS3 style with a linear-gradient fill and a rounded border. This will reduce browser compatibility a little bit, but all modern browsers support this functionality. Add Comment
[Geoserver-devel] [JIRA] (GEOS-8133) WMS layout:css-legend sometimes causes 360 W coordinate shift
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8133 WMS layout:css-legend sometimes causes 360 W coordinate shift Issue Type: Bug Affects Versions: 2.11.0, 2.12-beta Assignee: Unassigned Components: web, WMS Created: 10/May/17 12:36 AM Priority: Medium Reporter: Torben Barsballe If I make a WMS request with FORMAT_OPTIONS=layout:css-legend, the result will (sometimes) be shifted about 360 degrees west. See attached screenshots. So far, I have only observed this with single-band greyscale raster images, including the Arc_Sample layer included in the default data dir. This is also adversely affecting the Style Editor, which uses the layout:css-legend option Add Comment
[Geoserver-devel] [JIRA] (GEOS-8117) KVP parsing may fail if service or version is not set
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8117 KVP parsing may fail if service or version is not set Issue Type: Bug Assignee: Unassigned Components: WCS, WFS, WMS Created: 28/Apr/17 10:13 PM Priority: Medium Reporter: Torben Barsballe So far, I have only observed issues with WFS requests. Omitting the "service=wfs" parameter from a KVP-encoded request generally works just fine, as long as you are using the applicable virtual service endpoint. However, sometimes it doesn't. All testing is done with a GeoServer 2.10.2 installation with no extensions: With service=wfs: http://localhost:8080/geoserver/wfs?service=wfs=GetFeature=sf:roads=2.0.0 returns all property values for all features in sf:roads http://localhost:8080/geoserver/wfs?service=wfs=GetFeature=sf:roads=2.0.0= returns all property values for all features in sf:roads http://localhost:8080/geoserver/wfs?service=wfs=GetFeature=sf:roads=2.0.0=* returns all property values for all features in sf:roads http://localhost:8080/geoserver/wfs?service=wfs=GetFeature=sf:roads=2.0.0=cat returns all values for cat property for all features in sf:roads http://localhost:8080/geoserver/wfs?service=wfs=GetFeature=sf:roads=2.0.0=cat,label returns all values for cat and label properties for all features in sf:roads Without service=wfs: http://localhost:8080/geoserver/wfs?request=GetFeature=sf:roads=2.0.0 returns all property values for all features in sf:roads http://localhost:8080/geoserver/wfs?request=GetFeature=sf:roads=2.0.0= java.lang.NullPointerException http://localhost:8080/geoserver/wfs?request=GetFeature=sf:roads=2.0.0=*
[Geoserver-devel] [JIRA] (GEOS-8115) LDAP User/Group service configuration - duplicate field
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8115 LDAP User/Group service configuration - duplicate field Issue Type: Bug Assignee: Unassigned Created: 27/Apr/17 11:29 PM Priority: Medium Reporter: Torben Barsballe When construction a new ldap user/group service, there is a duplicate field under "User lookup options" (see attached screenshot): "Filter to search all users (leave blank to derive from attribute)" is shown twice. Based on the Group Lookup Options above, I think the second field is supposed to be "Filter to search user by name (leave blank to derive from attribute)", but I am not certain. Add Comment This message was sent by Atlassian JIRA
[Geoserver-devel] [JIRA] (GEOS-8110) Making a WMS request with no Layers results in an IndexOutOfBoundsException
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8110 Making a WMS request with no Layers results in an IndexOutOfBoundsException Issue Type: Bug Assignee: Unassigned Created: 25/Apr/17 6:01 PM Priority: Medium Reporter: Torben Barsballe The WMS response is: java.lang.StringIndexOutOfBoundsException: String index out of range: -1 String index out of range: -1 With the corresponding exception: java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.AbstractStringBuilder.setLength(AbstractStringBuilder.java:207) at java.lang.StringBuffer.setLength(StringBuffer.java:192) at org.geoserver.wms.WMSWorkspaceQualifier.toCommaSeparatedList(WMSWorkspaceQualifier.java:116) at org.geoserver.wms.WMSWorkspaceQualifier.qualifyLayerNamesKVP(WMSWorkspaceQualifier.java:68) at org.geoserver.wms.WMSWorkspaceQualifier.qualifyRequest(WMSWorkspaceQualifier.java:30) at org.geoserver.ows.WorkspaceQualifyingCallback.serviceDispatched(WorkspaceQualifyingCallback.java:44) at org.geoserver.ows.Dispatcher.fireServiceDispatchedCallback(Dispatcher.java:575) at org.geoserver.ows.Dispatcher.service(Dispatcher.java:570) at org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:245) at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:147) at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:50) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893) at
[Geoserver-devel] [JIRA] (GEOS-8107) WMS request against geotiff at lower resolution than source returns a white image
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8107 WMS request against geotiff at lower resolution than source returns a white image Issue Type: Bug Assignee: Unassigned Components: WMS Created: 21/Apr/17 9:41 PM Priority: Medium Reporter: Torben Barsballe When requesting a small region of a layer (backed by a geotiff store), at a resolution lower than the source image, a blank white image is returned. This was reproduces using world.tiff (attached), and the following WMS requests: This returns a grey rectangle (as expected): http://localhost:8080/geoserver/importer/wms?service=WMS=1.1.0=GetMap=importer:world=raster=-120.0,35,-100,45=42=21=EPSG:4326=image/png Reducing width and height to 40 and 20 respectively results in a white rectangle: http://localhost:8080/geoserver/importer/wms?service=WMS=1.1.0=GetMap=importer:world=raster=-120.0,35,-100,45=40=20=EPSG:4326=image/png Add Comment
[Geoserver-devel] [JIRA] (GEOS-8106) GeoServer Home Page missing information messages
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8106 GeoServer Home Page missing information messages Issue Type: Bug Affects Versions: 2.11-beta, 2.11-RC1, 2.11.0 Assignee: Unassigned Created: 21/Apr/17 6:53 PM Priority: Medium Reporter: Torben Barsballe The GeoServer Home page is missing the standard information messages (Strong cryptography available / not available, change your master password, etc.). This only appears to affect the 2.11.x series. A fix for the issue already exists on master here: https://github.com/geoserver/geoserver/commit/e0b67098dd270ef56f20741abeaeef72bf3f2a95 This should be backported to 2.11.x Add Comment
[Geoserver-devel] [JIRA] (GEOS-8101) Generating a raster SLD style from template produces a functionally invalid style
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-8101 Generating a raster SLD style from template produces a functionally invalid style Issue Type: Bug Affects Versions: 2.9.3, 2.10.1, 2.11.0, 2.12-beta Assignee: Unassigned Created: 21/Apr/17 2:11 AM Priority: Medium Reporter: Torben Barsballe Continuation of GEOS-7759 Closed . The fix introduced by that issue results in a style of the form: opengeo_i_3001a1 A raster style Raster 1.0 While this is formally valid, it never actually produces an image - Raster means only apply this style to feature types named raster. This should be replaced with Feature, which acts as a wild card. Add Comment
[Geoserver-devel] [JIRA] (GEOS-8002) Style does not display when using recode
Title: Message Title
Torben Barsballe created an issue
GeoServer / GEOS-8002
Style does not display when using recode
Issue Type:
Bug
Assignee:
Unassigned
Created:
21/Feb/17 11:46 PM
Priority:
Medium
Reporter:
Torben Barsballe
The following style works fine:
define:
label: ${fsmap_metadata_bean_rm}
fill-color: '#AA'
font-family: Lucida Sans Demibold
font-size: 20.0
font-style: normal
font-weight: normal
placement: point
define:
stroke-color: '#FF'
stroke-opacity: '1.0'
stroke-width: 0.4
stroke-linejoin: bevel
name: test_na_us_bean_rm_zones_YSLD_working
title: Relative Maturity style
feature-styles:
- name: name
rules:
- filter: ${fsmap_metadata_bean_rm = 'Zone 00'}
symbolizers:
- text:
<<: *textstyle
- polygon:
<<: *polystyle
fill-color: '#92C5DE'
- filter: ${fsmap_metadata_bean_rm = 'Zone 0'}
symbolizers:
- text:
<<: *textstyle
- polygon:
<<: *polystyle
fill-color: '#D1E5F0'
- filter: ${fsmap_metadata_bean_rm = 'Zone 1'}
symbolizers:
- text:
<<: *textstyle
- polygon:
<<: *polystyle
fill-color: '#FFF7EC'
- filter: ${fsmap_metadata_bean_rm = 'Zone 2'}
symbolizers:
- text:
<<: *textstyle
- polygon:
<<: *polystyle
fill-color: '#FEE8C8'
- filter: ${fsmap_metadata_bean_rm = 'Zone 3'}
symbolizers:
- text:
<<: *textstyle
- polygon:
<<: *polystyle
fill-color: '#FDBB84'
- filter: ${fsmap_metadata_bean_rm = 'Zone 4'}
symbolizers:
- text:
<<: *textstyle
- polygon:
<<: *polystyle
fill-color: '#FC8D59'
- filter: ${fsmap_metadata_bean_rm = 'Zone 5'}
symbolizers:
- text:
<<: *textstyle
- polygon:
<<: *polystyle
fill-color: '#EF6548'
- filter: ${fsmap_metadata_bean_rm = 'Zone 6'}
symbolizers:
[Geoserver-devel] [JIRA] (GEOS-7987) CatalogPostModifyEvent should track modified properties
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7987 CatalogPostModifyEvent should track modified properties Issue Type: Improvement Assignee: Unassigned Created: 09/Feb/17 8:19 PM Priority: Medium Reporter: Torben Barsballe CatalogPostModifyEvent should track modified properties, similar to CatalogModifyEvent CatalogModifyEvent is triggered before the change is actually made, while CatalogPostModifyEvent is triggered after. Knowing what has changed is useful in both cases. Add Comment This message was sent by Atlassian JIRA (v1000.747.0#100028-sha1:6f58f37)
[Geoserver-devel] [JIRA] (GEOS-7974) REST json/xml workspaces response does not show default ws
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7974 REST json/xml workspaces response does not show default ws Issue Type: Improvement Assignee: Unassigned Components: REST Created: 03/Feb/17 5:29 PM Priority: Lowest Reporter: Torben Barsballe Navigating to geoserver/rest/worxspaces.html, the default workspace is indicated in the list of workspaces. If you instead query geoserver/rest/worxspaces.xml or geoserver/rest/worxspaces.json, you cannot see which workspace is the default. This could be improved, so that all formats indicate the default workspace. Add Comment
[Geoserver-devel] [JIRA] (GEOS-7951) Update style page to OL3
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7951 Update style page to OL3 Issue Type: Task Assignee: Torben Barsballe Created: 27/Jan/17 7:46 PM Priority: Medium Reporter: Torben Barsballe The GeoServer Style Page preview currently uses OL2, and should be upgraded to OL3 Add Comment This message was sent by Atlassian JIRA (v1000.718.3#100026-sha1:529d721)
[Geoserver-devel] [JIRA] (GEOS-7936) Server restart required to register LDAP roles
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7936 Server restart required to register LDAP roles Issue Type: Improvement Affects Versions: 2.10.1 Assignee: Unassigned Components: Security Created: 19/Jan/17 1:44 AM Priority: Medium Reporter: Torben Barsballe I was testing out the GeoServer Authentication with LDAP tutorial, and ran into this issue. After Step 5 of Map LDAP groups to GeoServer roles , the users with administrative roles (e.g. bill) do not behave as administrators, but rather as regular users. Once restarting GeoServer, the users with administrative roles behave as administrators, as expected. Add Comment
[Geoserver-devel] [JIRA] (GEOS-7931) Improved REST API Documentation
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7931 Improved REST API Documentation Issue Type: Improvement Assignee: Unassigned Components: Documentation, REST Created: 17/Jan/17 1:29 AM Priority: Medium Reporter: Torben Barsballe The REST API documentation has been a fairly consistent cause for complaint among GeoServer users, and would benefit from a considerable revamp. Looking at the 70+ REST API tickets , doc fixes may close a large portion of them, as many of those are due to documentation confusion. The MapBox REST API provides a good template with info / curl example / request / response. Compare: https://www.mapbox.com/api-documentation/#datasets http://docs.geoserver.org/latest/en/user/rest/api/datastores.html Approach: Review the REST API tickets (above) and prioritize what to focus on for rest api docs. Refactor current REST API content into a more approachable presentation, with API structure documentation followed by specific examples. Design: Document Each REST Endpoint (Syntax, supported request types/ response types/codes). Follow up with one or more relevant examples, such that examples and documentation for any given endpoint is in the same place. For appearance, aim towards more of a field-list kind of presentation, so not side by side like the mapbox page. We will have to decide what to do with the more complex examples that use several different endpoints. They can probably remain in a dedicated examples section. Nice-to-haves:
[Geoserver-devel] [JIRA] (GEOS-7865) Revert changes when a CatalogException is thrown
Title: Message Title
Torben Barsballe created an issue
GeoServer / GEOS-7865
Revert changes when a CatalogException is thrown
Issue Type:
Improvement
Assignee:
Unassigned
Created:
17/Nov/16 8:25 PM
Priority:
Medium
Reporter:
Torben Barsballe
From "CatalogListener.java":
* In general the catalog protects itself against misbehaved listeners that throw * exceptions. However sometimes it is the case in which a listener must report an error * via exception. For such purposes {@link CatalogException} should be thrown.
When the catalog actually recieves a CatalogException, it just re-throws it and does not do any work to revert any changes that have been made. This can cause various problems. For example, for
GEOS-4754 Open , when we try and create a layer group it gets added to the catalog, then the persistor throws a CatalogException, meaning that the layer group is not persisted. However, the act of adding the layer group to the catalog is never reverted. A couple things need to be done here: a) Some documentation work to clarify the pupose / intended usage of CatalogException, particularily whether or not the catalog is responsible for reverting changes, or if this is a responsibility of whatever is using the catalog / catching the CatalogException. b) If CatalogException is intended to be thrown upstream (which is appears it is), the Catalog interface should be modified to indicate that certain methods can throw CatalogException. This is a rather substantial API change
[Geoserver-devel] [JIRA] (GEOS-7863) Allow docs to expand beyond 600px
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7863 Allow docs to expand beyond 600px Issue Type: Improvement Assignee: Unassigned Components: Documentation Created: 17/Nov/16 7:00 PM Priority: Medium Reporter: Torben Barsballe The current geoserver docs have a static 600px width. Some more advanced CSS rules should be added to support a more diverse range of screen resolutions (e.g. mobile, plus larger 1280px screens) Add Comment This message was sent by Atlassian
[Geoserver-devel] [JIRA] (GEOS-7858) Deleting nested LayerGroups via catalog.remove will break the catalog
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7858 Deleting nested LayerGroups via catalog.remove will break the catalog Issue Type: Bug Assignee: Unassigned Created: 16/Nov/16 9:44 PM Priority: Medium Reporter: Torben Barsballe If you delete a layerGroup that is contained within another layerGroup by any method that uses Catalog.remove() (rather than CascadingDeleteVisitor), you will corrupt the catalog; The deleteion will succed but not update the containing layer group, meaning that any further events to access the remaining layer group will fail with the following error: Caused by: java.lang.NullPointerException at org.geoserver.security.SecureCatalogImpl.checkAccess(SecureCatalogImpl.java:631) at org.geoserver.security.SecureCatalogImpl.checkAccess(SecureCatalogImpl.java:490) at org.geoserver.security.SecureCatalogImpl.checkAccess(SecureCatalogImpl.java:634) at org.geoserver.security.SecureCatalogImpl.filterGroups(SecureCatalogImpl.java:959) at org.geoserver.security.SecureCatalogImpl.getLayerGroupsByWorkspace(SecureCatalogImpl.java:328) at org.geoserver.catalog.impl.AbstractFilteredCatalog.getLayerGroupsByWorkspace(AbstractFilteredCatalog.java:259) at org.geoserver.catalog.impl.AbstractCatalogDecorator.getLayerGroupsByWorkspace(AbstractCatalogDecorator.java:466) at org.geoserver.catalog.impl.LocalWorkspaceCatalog.getLayerGroupsByWorkspace(LocalWorkspaceCatalog.java:210) at org.geoserver.catalog.rest.LayerGroupListResource.handleListGet(LayerGroupListResource.java:32) at org.geoserver.catalog.rest.LayerGroupListResource.handleListGet(LayerGroupListResource.java:1) at org.geoserver.catalog.rest.AbstractCatalogListResource.handleObjectGet(AbstractCatalogListResource.java:41) at org.geoserver.rest.ReflectiveResource.handleGet(ReflectiveResource.java:89) ... 89 more This occurs because the LayerGroup still holds a reference to the
[Geoserver-devel] [JIRA] (GEOS-7857) Cascade Delete fails for a layer group contained within another layer group
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7857 Cascade Delete fails for a layer group contained within another layer group Issue Type: Improvement Assignee: Unassigned Created: 16/Nov/16 7:39 PM Priority: Medium Reporter: Torben Barsballe If you try to apply a CascadeDeleteVisitor to a layer group that is itself contained within another layer group, you will get the following error: java.lang.IllegalArgumentException: Layer group has different number of styles than layers at org.geoserver.catalog.impl.CatalogImpl.validate(CatalogImpl.java:845) at org.geoserver.catalog.impl.CatalogImpl.save(CatalogImpl.java:938) at org.geoserver.security.SecureCatalogImpl.save(SecureCatalogImpl.java:1315) at org.geoserver.catalog.impl.AbstractFilteredCatalog.save(AbstractFilteredCatalog.java:740) at org.geoserver.catalog.impl.AbstractCatalogDecorator.save(AbstractCatalogDecorator.java:446) at org.geoserver.catalog.impl.LocalWorkspaceCatalog.save(LocalWorkspaceCatalog.java:218) at org.geoserver.catalog.CascadeDeleteVisitor.visit(CascadeDeleteVisitor.java:273) ... Additionally, if you try to apply the CascadeDeleteVisitor to a store or workspace, when there is a global layer group containing only layers from that store/workspace and other layer groups containing such layers, the nested layer groups will not be removed properly, and you will wind up with empty layer groups that do not get automatically removed by the visitor.
[Geoserver-devel] [JIRA] (GEOS-7852) REST API implementation for setting defaults violates Catalog API
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7852 REST API implementation for setting defaults violates Catalog API Issue Type: Improvement Assignee: Unassigned Components: REST Created: 15/Nov/16 1:32 AM Priority: Medium Reporter: Torben Barsballe The REST API implementation of handleObjectPut for NamespaceResource and WorkspaceResource has an odd implementation for case of setting the default value. It passes a partial (name / prefix set, everything else null, including Id) Info object to catalog.setDefault[Workspace/Namespace]: https://github.com/geoserver/geoserver/blob/master/src/restconfig/src/main/java/org/geoserver/catalog/rest/NamespaceResource.java#L88 https://github.com/geoserver/geoserver/blob/master/src/restconfig/src/main/java/org/geoserver/catalog/rest/WorkspaceResource.java#L121 Just looking at the CatalogInfo / CatalogFacade interfaces, the behaviour for this is undefined, but the implication is that you should be passing valid Catalig objects to the CatalogFacade method. Looking at the implementation, it appears this only works because there is a special case hardcoded in to handle it: https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/geoserver/catalog/impl/DefaultCatalogFacade.java#L645 https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/geoserver/catalog/impl/DefaultCatalogFacade.java#L744 The REST API implementation should be fixed.
[Geoserver-devel] [JIRA] (GEOS-7839) Modifying CatalogInfo objects with the REST API makes them permanently unusable
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7839 Modifying CatalogInfo objects with the REST API makes them permanently unusable Issue Type: Bug Assignee: Unassigned Created: 07/Nov/16 9:51 PM Environment: If you use the REST API to modify a LayerInfo object, subsequent request (get, modify, delete, etc.) will fail, with the error No property null found on entity class com.sun.proxy.$Proxy171 to bind constructor parameter to! This occurs because the AttributionInfo property of the LayerInfo object is wrapped in a proxy when it gets saved to Redis after the layer is modified. This error occurs even if you don't modify the AttributionInfo. While I have not tested, I assume this also affects other CatalogInfo objects that have info objects as properties, such as LayerGroupInfo or StyleInfo. Priority: Medium Reporter: Torben Barsballe Add Comment
[Geoserver-devel] [JIRA] (GEOS-7831) YSLD Validator not called by Style Page
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7831 YSLD Validator not called by Style Page Issue Type: Bug Assignee: Unassigned Created: 01/Nov/16 9:09 PM Priority: Medium Reporter: Torben Barsballe If you try to validate a YSLD style from the GeoServer Style Editor (Wicket Page), it blindly returns "Success". This needs to be connected to the actual YSLD Validator so that we can validate YSLD styles. Add Comment This message was sent by Atlassian JIRA (v1000.482.3#100017-sha1:2ae3eee)
[Geoserver-devel] [JIRA] (GEOS-7828) Some Style Page errors not shown when clicking "Submit"
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7828 Some Style Page errors not shown when clicking "Submit" Issue Type: Bug Affects Versions: 2.10.0 Assignee: Unassigned Created: 29/Oct/16 1:57 AM Priority: Medium Reporter: Torben Barsballe If I try and rename a style to an already existing style and click submit, I will be returned to the Style list page with no error message. The style I was editing will not be renamed. Add Comment This message was sent by Atlassian
[Geoserver-devel] [JIRA] (GEOS-7822) REST PUT property update on ServiceInfo does not work properly for primitive properties
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7822 REST PUT property update on ServiceInfo does not work properly for primitive properties Issue Type: Bug Affects Versions: 2.10.0, 2.9.2 Assignee: Unassigned Created: 28/Oct/16 12:03 AM Priority: Medium Reporter: Torben Barsballe Doing a REST PUT agains any ServiceInfo object (e.g WMSInfo, WFSInfo, ...) will set all primitive values not included in the request to their java defaults. This includes setting all boolean values (including enabled) to false. This is effectively the same as GEOS-3964 Closed , except for ServiceInfo implementations Add Comment
[Geoserver-devel] [JIRA] (GEOS-7821) REST API services settings.html throws errors for null values
Title: Message Title
Torben Barsballe created an issue
GeoServer / GEOS-7821
REST API services settings.html throws errors for null values
Issue Type:
Bug
Affects Versions:
2.10.0, 2.9.2
Assignee:
Unassigned
Created:
27/Oct/16 11:56 PM
Priority:
Medium
Reporter:
Torben Barsballe
If you do a REST get against one of the OWS service settings html endpoints (e.g. rest/services/wfs/settings) and any of the values are null, you will see an error similar to the following:
WFS Enabled: "true"
Strict CITE compliance: "false"
Maintainer: " _expression_ properties.maintainer is undefined on line 13, column 23 in wfsSettings.ftl. The problematic instruction: -- ==> ${properties.maintainer} [on line 13, column 21 in wfsSettings.ftl] -- Java backtrace for programmers: -- freemarker.core.InvalidReferenceException: _expression_ properties.maintainer is undefined on line 13, column 23 in wfsSettings.ftl. at freemarker.core.TemplateObject.assertNonNull(TemplateObject.java:125) at freemarker.core._expression_.getStringValue(_expression_.java:118) at freemarker.core._expression_.getStringValue(_expression_.java:93) at freemarker.core.DollarVariable.accept(DollarVariable.java:76) at freemarker.core.Environment.visit(Environment.java:221) at freemarker.core.MixedContent.accept(MixedContent.java:92) at freemarker.core.Environment.visit(Environment.java:221) at freemarker.core.Environment.process(Environment.java:199) at freemarker.template.Template.process(Template.java:237) at org.restlet.ext.freemarker.TemplateRepresentation.write(TemplateRepresentation.java:112) at com.noelios.restlet.http.HttpServerCall.writeResponseBody(HttpServerCall.java:342) at com.noelios.restlet.http.HttpServerCall.sendResponse(HttpServerCall.java:306) at
[Geoserver-devel] [JIRA] (GEOS-7752) Renaming default styles causes style duplication
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7752 Renaming default styles causes style duplication Issue Type: Bug Assignee: Unassigned Created: 21/Sep/16 12:20 AM Priority: Medium Reporter: Torben Barsballe If you try and rename one of the default geoserver styles (point, polygon, line etc.) the style will get recreated when you restart geoserver. This will result in having two differently named styles pointing to the same style file (such that edits to one are reflected in the other). The best approch hear is probably to disallow users from renaming the default styles, given that deletion is already disallowed Add Comment This message was sent by Atlassian JIRA
[Geoserver-devel] [JIRA] (GEOS-7747) JDBCStore stores style configuration files
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7747 JDBCStore stores style configuration files Issue Type: Bug Affects Versions: 2.9.1, 2.10-M0 Assignee: Unassigned Components: JDBCStore Created: 19/Sep/16 8:45 PM Priority: Medium Reporter: Torben Barsballe JDBCStore tracks directories via include/exclude. JDBCStore includes the styles/ folder in order to store style (.sld) files and external graphics. However, the styles/ folder already contains mixed xml configuration (for the StyleInfo objects) and style files. This means that in addition to storeing style files and external graphics (as expected) JDBCStore is also storing style configuration (NOT expected) In addition, when jdbcconfig (which is intended to often be used alongside jdbcstore) installed and enabled (before enabling jdbcstore), both jdbcstore and jdbcconfig contain a copy of the
[Geoserver-devel] [JIRA] (GEOS-7748) JDBCStore does not store workspaced styles or graphics
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7748 JDBCStore does not store workspaced styles or graphics Issue Type: Bug Assignee: Unassigned Created: 19/Sep/16 8:49 PM Priority: Medium Reporter: Torben Barsballe The GeoServer data directory contains a styles/ folder for storing SLD files and external graphics. Currently, this is managed by JDBCStore. However, for each workspace, there is also a /workspaces//styles folder which contains styles and icons for that workspace, similar to how the top-level styles folder contains global styles. These are not being stored by JDBCStore. Add Comment This message was sent by Atlassian JIRA (v1000.319.1#100012-sha1:913341f)
[Geoserver-devel] [JIRA] (GEOS-7742) SLD Files created in old data dir when JDBCStore enabled
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7742 SLD Files created in old data dir when JDBCStore enabled Issue Type: Bug Assignee: Unassigned Components: JDBCStore Created: 14/Sep/16 12:09 AM Priority: Medium Reporter: Torben Barsballe With JDBCStore enabled, I create a new style. This style is correctly inserted into the JDBCStore. If I then try to assign the style to a layer, the style gets created within the old data directory. This should not happen! Note: The style (sld file) gets created in the data directory gets created as soon as I select it from the drop-down menu on the Publishing tab of the layer, presumably as part of the process that renders the style preview. Add Comment
[Geoserver-devel] [JIRA] (GEOS-7741) External graphics within the data dir do not work with JDBCStore
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7741 External graphics within the data dir do not work with JDBCStore Issue Type: Improvement Affects Versions: 2.9.1 Assignee: Unassigned Components: JDBCStore Created: 13/Sep/16 11:56 PM Priority: Medium Reporter: Torben Barsballe After setting up JDBCStore, I add a graphic to the GeoServer styles directory using curl -v -u admin:geoserver -XPUT -H "Content-type: image/png" --data-binary @smileyface.png http://localhost:8080/geoserver/rest/resource/styles/smileyface.png I then create a new style: icon smileyface smileface image/png If I try to render this style on a layer, I just get grey boxes instead of images. Looking through the debugger, I have traced this issue down to GeoServerDataDirectory line: 1201 . Here, we explicitly convert the resource path into a file path, which causes GeoServer to look in the old data directory (instead of the JDBC Resource Store), which does not contain the image. Debug stack:
[Geoserver-devel] [JIRA] (GEOS-7740) JDBCStore incompatible with Hazelcast Clustering extension
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7740 JDBCStore incompatible with Hazelcast Clustering extension Issue Type: Improvement Affects Versions: 2.9.1 Assignee: Unassigned Created: 13/Sep/16 8:05 PM Environment: Priority: Medium Reporter: Torben Barsballe With both jdbcstore and hz-cluster installed, I am getting some critical failures revolving around com.hazelcast.nio.serialization.HazelcastSerializationException: There is no suitable serializer for class org.geoserver.platform.resource.ResourceNotification If I try to update a Resource in JDBCStore using a PUT, I get a HTTP 500 response, but the resource gets updated successfully. Looking in the logs, I see the following error: com.hazelcast.nio.serialization.HazelcastSerializationException: There is no suitable serializer for class org.geoserver.platform.resource.ResourceNotification at com.hazelcast.nio.serialization.SerializationServiceImpl.toData(SerializationServiceImpl.java:215) at com.hazelcast.nio.serialization.SerializationServiceImpl.toData(SerializationServiceImpl.java:200) at com.hazelcast.spi.impl.NodeEngineImpl.toData(NodeEngineImpl.java:180) at com.hazelcast.topic.impl.TopicProxy.publish(TopicProxy.java:33) at org.geoserver.cluster.hazelcast.HzResourceNotificationDispatcher.changed(HzResourceNotificationDispatcher.java:51) at org.geoserver.jdbcstore.JDBCResourceStore$JDBCResource$CachingOutputStreamWrapper.close(JDBCResourceStore.java:364) at org.geoserver.rest.util.IOUtils.copyStream(IOUtils.java:688) at
[Geoserver-devel] [JIRA] (GEOS-7733) Move IOUtils from gs-main to gs-platform
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7733 Move IOUtils from gs-main to gs-platform Issue Type: Improvement Assignee: Unassigned Created: 08/Sep/16 11:46 PM Fix Versions: 2.10-beta Priority: Medium Reporter: Torben Barsballe IOUtils contains a bunch of usefull File and IO utilities, including a very thorough rename method. However, IOUtils is contained in the gs-main project, which has gs-platform as a dependency FileSystemResouce (in gs-platform) is currently using the plain java File rename, leading to GEOS-7651 Open . It would be better to have utility classes such as IOUtils as far upstream as possible (e.g. in gs-platform rather than gs-main). IOUtils currently contains a couple of methods that depend on classes in gs-main (XStreamPersister related stuff, which could be refactored out to its own utility method). In order to mitigate API changes, we can retain the gs-main org.geoserver.data.util.IOUtils as a deprecated class for the duration of 2.10. To limit code duplication, it will extend the new IOUtils in gs-platform. Add Comment
[Geoserver-devel] [JIRA] (GEOS-7730) Renaming a style after failing validation will duplicate the style
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7730 Renaming a style after failing validation will duplicate the style Issue Type: Bug Affects Versions: 2.9.1, 2.10-M0 Assignee: Unassigned Created: 08/Sep/16 12:00 AM Priority: Medium Reporter: Torben Barsballe Steps to reproduce: 1. Start GeoServer 2. Edit an existing style and delete the name. Click "Submit". You should get an error message along the lines of "Field 'Name' is required". 3. Fill the name field in with something different from the original name of the style. 4. Click "Submit". You will be returned to the style list, and will see the renamed style. 5. Restart GeoServer. 6. Go to the style list. You will see both the original style name and the renamed style as seperate entries. Some things to note: This only appears to affect Style, not Layer, LayerGroup, etc. This affects both the old style page (pre 2.10) and the new style page (post 2.10). While I have only tested 2.9.x and master, I assume this affects 2.8 and earlier as well. Add Comment
[Geoserver-devel] [JIRA] (GEOS-7729) GeoServer Style Page - Field validation messages missing
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7729 GeoServer Style Page - Field validation messages missing Issue Type: Bug Affects Versions: 2.10-M0 Assignee: Torben Barsballe Created: 07/Sep/16 10:29 PM Priority: Medium Reporter: Torben Barsballe When trying to submit a style with invalid data, the form runs validation and finds errors, but does not actually dispay the errors on the page. For example, if trying to submit a style with no name, the submit fails but there is no error message indicating why. Add Comment
[Geoserver-devel] [JIRA] (GEOS-7700) WMS in EPSG:3857 discards geometry
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7700 WMS in EPSG:3857 discards geometry Issue Type: Bug Assignee: Unassigned Created: 27/Aug/16 2:48 PM Priority: Medium Reporter: Torben Barsballe Using http://www.naturalearthdata.com/http//www.naturalearthdata.com/download/10m/cultural/ne_10m_admin_1_states_provinces.zip for layer data. Doing a WMS request in EPSG:3857 (Web Mercator) against this layer results in the vector geometry being truncated beyond the bounds of the projection. This results in malformed geometries - see attached examples. This should throw an error rather than returning malformed geometry. Add Comment This message was sent by Atlassian JIRA
[Geoserver-devel] [JIRA] (GEOS-7694) GeoServer Style Page - Run validate when clicking "Apply"
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7694 GeoServer Style Page - Run validate when clicking "Apply" Issue Type: Improvement Assignee: Unassigned Created: 21/Aug/16 5:10 PM Priority: Medium Reporter: Torben Barsballe When the "Apply" button is clicked on the GeoServer style page, the style should be validated and any errors shown (note that this functionality is already implemented for the validate button, sans saving the style) Add Comment This message was sent by Atlassian JIRA (v1000.253.3#100011-sha1:6da8fdb)
[Geoserver-devel] [JIRA] (GEOS-7693) GeoServer style page - Exception previewing with WMS layer
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7693 GeoServer style page - Exception previewing with WMS layer Issue Type: Bug Affects Versions: 2.10-M0 Assignee: Unassigned Created: 21/Aug/16 4:53 PM Fix Versions: 2.10-beta Priority: Medium Reporter: Torben Barsballe This one requires you to setup a WMS cascaded layer, then go into an existing style, layer attributes, choose it for preview, and boom. This one and the previous are likely occurring in the CSS editor already, but obviously here they are there for everybody to stumble upon: 10 ago 13:40:51 WARN [RequestCycleExtra] - 10 ago 13:41:52 ERROR [wicket.MarkupContainer] - Unable to find component with id 'attributePanel' in [LayerAttributePanel [Component id = panel]] Expected: 'styleForm:context:panel:attributePanel'. Found with similar names: '' 10 ago 13:41:52 WARN [RequestCycleExtra] - 10 ago 13:41:52 WARN [RequestCycleExtra] - Handling the following exception Unable to find component with id 'attributePanel' in [LayerAttributePanel [Component id = panel]] Expected: 'styleForm:context:panel:attributePanel'. Found with similar names: '' MarkupStream: [markup = file:/home/aaime/devel/git-gs/src/web/wms/target/classes/org/geoserver/wms/web/data/LayerAttributePanel.html Previewing on layer: , index = 8, current = '' (line 0, column 0)] at org.apache.wicket.markup.MarkupStream.throwMarkupException(MarkupStream.java:526) at org.apache.wicket.MarkupContainer.renderNext(MarkupContainer.java:1308) at
[Geoserver-devel] [JIRA] (GEOS-7692) GeoServer Style Page - Exception with unreachable layer
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7692 GeoServer Style Page - Exception with unreachable layer Issue Type: Bug Affects Versions: 2.10-M0 Assignee: Unassigned Created: 21/Aug/16 4:52 PM Fix Versions: 2.10-beta Priority: Medium Reporter: Torben Barsballe This one requires a data dir with a disabled and unreachable layer, e.g., configure a layer from postgis, drop it, restart GeoServer. Then go into an existing style, layer attributes, search for said layer, you will be able to choose it, and then the page goes boom: 10 ago 13:39:28 WARN [RequestCycleExtra] - Handling the following exception org.apache.wicket.core.request.handler.ListenerInvocationNotAllowedException: Behavior rejected interface invocation. Component: [GeoServerAjaxFormLink [Component id = link]] Behavior: org.apache.wicket.ajax.markup.html.form.AjaxSubmitLink$1@55549645 Listener: [RequestListenerInterface name=IBehaviorListener, method=public abstract void org.apache.wicket.behavior.IBehaviorListener.onRequest()] at org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:237) 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:865) at org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64) at
[Geoserver-devel] [JIRA] (GEOS-7691) GeoServer Style Page - Preview reloads upon save
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7691 GeoServer Style Page - Preview reloads upon save Issue Type: Bug Affects Versions: 2.10-M0 Assignee: Unassigned Created: 21/Aug/16 4:49 PM Fix Versions: 2.10-beta Priority: Medium Reporter: Torben Barsballe When clicking the apply button, the Style page gets reloaded. If you are on the preview tab, this means your location and zoom level get reset. The CSS Style page did not behave like this, but rather managed to do a save in place without reloading the page. The fix to this will need to be compatible with GEOS-7690 Open . Add Comment
[Geoserver-devel] [JIRA] (GEOS-7690) GeoServer Style Page - Edits getting lost when switching tabs
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7690 GeoServer Style Page - Edits getting lost when switching tabs Issue Type: Bug Affects Versions: 2.10-M0 Assignee: Unassigned Created: 21/Aug/16 4:46 PM Fix Versions: 2.10-beta Priority: Medium Reporter: Torben Barsballe When making changes on the Data tab, and switching to another tab, edits are lost. ResourceConfigurationPage seems to have a special workaround to deal with this, we should be able to adapt this. Add Comment
[Geoserver-devel] [JIRA] (GEOS-7689) GeoServer Style Page - NotSerializableException
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7689 GeoServer Style Page - NotSerializableException Issue Type: Bug Affects Versions: 2.10-M0 Assignee: Torben Barsballe Created: 21/Aug/16 4:42 PM Fix Versions: 2.10-beta Priority: Medium Reporter: Torben Barsballe The following exception occurs occasionally. It is not readily reproducible, but has been reported by multiple people: 10 ago 10:38:25 WARN [checker.CheckingObjectOutputStream] - error delegating to writeObject : org.geoserver.catalog.impl.ResolvingProxy, path: /children 10 ago 10:38:25 ERROR [java.JavaSerializer] - Error serializing object class org.geoserver.wms.web.data.StyleEditPage [object=[Page class = org.geoserver.wms.web.data.StyleEditPage, id = 15, render count = 1]] org.apache.wicket.WicketRuntimeException: A problem occurred while trying to collect debug information about not serializable object at org.apache.wicket.serialize.java.JavaSerializer$SerializationCheckerObjectOutputStream.writeObjectOverride(JavaSerializer.java:282) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344) at org.apache.wicket.serialize.java.JavaSerializer.serialize(JavaSerializer.java:78) at org.apache.wicket.pageStore.AbstractPageStore.serializePage(AbstractPageStore.java:133) at org.apache.wicket.pageStore.DefaultPageStore.createSerializedPage(DefaultPageStore.java:281) at org.apache.wicket.pageStore.DefaultPageStore.storePage(DefaultPageStore.java:61) at org.apache.wicket.page.PageStoreManager$PersistentRequestAdapter.storeTouchedPages(PageStoreManager.java:403) at
[Geoserver-devel] [JIRA] (GEOS-7661) NumberFormatException on DecimalTextField with value NaN
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7661 NumberFormatException on DecimalTextField with value NaN Issue Type: Bug Affects Versions: 2.8.4, 2.9.0 Assignee: Unassigned Created: 27/Jul/16 10:37 PM Priority: Medium Reporter: Torben Barsballe This issue appears to have been introduced by GEOS-7621 Resolved . When a DecimalTextField or similar is passed the value NaN, then validated, a NumberFormatException is thrown: Caused by: java.lang.NumberFormatException at java.math.BigDecimal.(BigDecimal.java:494) at java.math.BigDecimal.(BigDecimal.java:383) at java.math.BigDecimal.(BigDecimal.java:806) at org.apache.wicket.util.convert.converter.AbstractNumberConverter.parse(AbstractNumberConverter.java:126) at org.apache.wicket.util.convert.converter.DoubleConverter.convertToObject(DoubleConverter.java:51) at org.geoserver.web.wicket.DecimalConverter.convertToObject(DecimalConverter.java:48) at org.apache.wicket.util.convert.converter.DoubleConverter.convertToObject(DoubleConverter.java:31) at org.apache.wicket.markup.html.form.FormComponent.convertInput(FormComponent.java:1183) at org.apache.wicket.markup.html.form.AbstractTextComponent.convertInput(AbstractTextComponent.java:129) at org.apache.wicket.markup.html.form.FormComponent.validate(FormComponent.java:1130) at org.apache.wicket.markup.html.form.Form$18.validate(Form.java:1948) at org.apache.wicket.markup.html.form.Form$ValidationVisitor.component(Form.java:177) at org.apache.wicket.markup.html.form.Form$ValidationVisitor.component(Form.java:161) at org.apache.wicket.util.visit.Visits.visitPostOrderHelper(Visits.java:274) at org.apache.wicket.util.visit.Visits.visitPostOrderHelper(Visits.java:262) at
[Geoserver-devel] [JIRA] (GEOS-7628) ResourceConfigurationPage.updateResource() does not visit children properly
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7628 ResourceConfigurationPage.updateResource() does not visit children properly Issue Type: Bug Assignee: Torben Barsballe Created: 08/Jul/16 7:30 PM Priority: Medium Reporter: Torben Barsballe When ResourceConfigurationPage.updateResource() was updated to use a lambda expersion, it was limited to visit TextField.class for no clear reason. This means that the method will only visit children that are TextFileds, and therfore no longer has any effect. See here for the commit in question. Add Comment This message was sent by Atlassian JIRA (v1000.141.1#14-sha1:5b3de17)
[Geoserver-devel] [JIRA] (GEOS-7606) GeoServer extension packages include httpclient-4.2.5.jar & httpcore-4.3.3.jar
Title: Message Title Torben Barsballe created an issue GeoServer / GEOS-7606 GeoServer extension packages include httpclient-4.2.5.jar & httpcore-4.3.3.jar Issue Type: Bug Assignee: Torben Barsballe Components: release Created: 25/Jun/16 12:49 AM Priority: Medium Reporter: Torben Barsballe The geoserver release process collects all jars for all extensions in a single maven process when building extensions. This means that when there are conflicting jar versions, it will choose some arbitrary version from among the valid ones. In this instance, various extension depend on numerous httpclient and httpcore versions: [INFO] org.geoserver.script:gs-script-groovy:jar:2.9-SNAPSHOT [INFO] \- org.geoscript:geoscript-groovy:jar:1.7-SNAPSHOT:compile [INFO]\- org.geotools:gt-netcdf:jar:15-SNAPSHOT:compile [INFO] \- edu.ucar:cdm:jar:4.6.2:compile [INFO] +- edu.ucar:httpservices:jar:4.6.2:runtime [INFO] | \- org.apache.httpcomponents:httpclient:jar:4.3.6:runtime [INFO] \- org.apache.httpcomponents:httpcore:jar:4.3.3:runtime [INFO] org.geoserver.community:gs-web-solr:jar:2.9-SNAPSHOT [INFO] \- org.apache.solr:solr-solrj:jar:4.9.0:compile [INFO]+- org.apache.httpcomponents:httpclient:jar:4.3.1:compile [INFO]+- org.apache.httpcomponents:httpcore:jar:4.3:compile [INFO]\- org.apache.httpcomponents:httpmime:jar:4.3.1:compile [INFO] org.geoserver.community:gs-wps-remote:jar:2.9-SNAPSHOT [INFO] \- org.igniterealtime.smack:smack-bosh:jar:4.0.3:compile [INFO]\- org.igniterealtime.jbosh:jbosh:jar:0.8.0:compile [INFO] \- org.apache.httpcomponents:httpclient:jar:4.3.3:compile [INFO] \- org.apache.httpcomponents:httpcore:jar:4.3.2:compile [INFO] org.geoserver.community:gs-gwc-s3:jar:2.9-SNAPSHOT [INFO] \-
