[Geoserver-devel] [JIRA] (GEOS-10044) WMS requests for a layergroup including a cql_filter are not cachable
Mauro Bartolomeoli ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ae5899f77-4ce7-4c27-89f9-34256c006cb7 ) *created* an issue GeoServer ( https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiMjNhNzI4ZWM1OGY3NDlkZDhhOWFmYzRlNzYwYTgwNWQiLCJwIjoiaiJ9 ) / Bug ( https://osgeo-org.atlassian.net/browse/GEOS-10044?atlOrigin=eyJpIjoiMjNhNzI4ZWM1OGY3NDlkZDhhOWFmYzRlNzYwYTgwNWQiLCJwIjoiaiJ9 ) GEOS-10044 ( https://osgeo-org.atlassian.net/browse/GEOS-10044?atlOrigin=eyJpIjoiMjNhNzI4ZWM1OGY3NDlkZDhhOWFmYzRlNzYwYTgwNWQiLCJwIjoiaiJ9 ) WMS requests for a layergroup including a cql_filter are not cachable ( https://osgeo-org.atlassian.net/browse/GEOS-10044?atlOrigin=eyJpIjoiMjNhNzI4ZWM1OGY3NDlkZDhhOWFmYzRlNzYwYTgwNWQiLCJwIjoiaiJ9 ) Issue Type: Bug Affects Versions: 2.19-RC Assignee: Mauro Bartolomeoli ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ae5899f77-4ce7-4c27-89f9-34256c006cb7 ) Components: GWC, WMS Created: 29/Apr/21 6:00 PM Priority: Medium Reporter: Mauro Bartolomeoli ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ae5899f77-4ce7-4c27-89f9-34256c006cb7 ) Layer groups are expanded to lists of simple layers, styles and filters in GetMapKvpRequestReader, so that at the lower level rendering only deals with simple layers. During this expansion if a filter is configured for a layergroup, this is applied to all the layers of the group. Unfortunately, there is a bug when this filter is configured via cql_filter instead of filter that impacts GWC capability to cache the layergroup if a parameter filter for FILTER has been configured. This happens because: * cql_filter is expanded and stored as filter in the request * the single cql_filter param is not removed / cleaned up * we finally have, in the rendered request, 1 cql_filter and N cloned filter configured * GWC has a check to disable caching when both cql_filter and filter are present and they are not equal TADAH! Caching is always disabled in our scenario. We suggest to change GetMapKvpRequestReader to store the expanded filter (coming from a cql_filter parameter) both in filter and cql_filter, so that GWC is happy to cache. ( https://osgeo-org.atlassian.net/browse/GEOS-10044#add-comment?atlOrigin=eyJpIjoiMjNhNzI4ZWM1OGY3NDlkZDhhOWFmYzRlNzYwYTgwNWQiLCJwIjoiaiJ9 ) Add Comment ( https://osgeo-org.atlassian.net/browse/GEOS-10044#add-comment?atlOrigin=eyJpIjoiMjNhNzI4ZWM1OGY3NDlkZDhhOWFmYzRlNzYwYTgwNWQiLCJwIjoiaiJ9 ) 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&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100157- sha1:45b74eb )___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-10015) Print extension is broken in recent versions
Mauro Bartolomeoli ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ae5899f77-4ce7-4c27-89f9-34256c006cb7 ) *created* an issue GeoServer ( https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiNGEwODBlYWI3NGQ3NDI3ZDlkZWY5Y2IyNDVhZjU2MzAiLCJwIjoiaiJ9 ) / Improvement ( https://osgeo-org.atlassian.net/browse/GEOS-10015?atlOrigin=eyJpIjoiNGEwODBlYWI3NGQ3NDI3ZDlkZWY5Y2IyNDVhZjU2MzAiLCJwIjoiaiJ9 ) GEOS-10015 ( https://osgeo-org.atlassian.net/browse/GEOS-10015?atlOrigin=eyJpIjoiNGEwODBlYWI3NGQ3NDI3ZDlkZWY5Y2IyNDVhZjU2MzAiLCJwIjoiaiJ9 ) Print extension is broken in recent versions ( https://osgeo-org.atlassian.net/browse/GEOS-10015?atlOrigin=eyJpIjoiNGEwODBlYWI3NGQ3NDI3ZDlkZWY5Y2IyNDVhZjU2MzAiLCJwIjoiaiJ9 ) Issue Type: Improvement Affects Versions: 2.19.0 Assignee: Unassigned Components: Mapfish print Created: 09/Apr/21 8:57 AM Priority: Medium Reporter: Mauro Bartolomeoli ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ae5899f77-4ce7-4c27-89f9-34256c006cb7 ) Calling http://localhost:8080/geoserver/pdf/info.json you get the following error: javax.servlet.ServletException: org.springframework.web.util.NestedServletException: Handler dispatch failed; nested exception is java.lang.NoSuchMethodError: org.json.JSONWriter.(Ljava/io/Writer;)V This should be related to the json-20180813.jar library that has a breaking change on methods used by the printing extension. See here how the mapfish-app application solved the same, reverting the library version: https://github.com/georchestra/georchestra/pull/2517/files ( https://osgeo-org.atlassian.net/browse/GEOS-10015#add-comment?atlOrigin=eyJpIjoiNGEwODBlYWI3NGQ3NDI3ZDlkZWY5Y2IyNDVhZjU2MzAiLCJwIjoiaiJ9 ) Add Comment ( https://osgeo-org.atlassian.net/browse/GEOS-10015#add-comment?atlOrigin=eyJpIjoiNGEwODBlYWI3NGQ3NDI3ZDlkZWY5Y2IyNDVhZjU2MzAiLCJwIjoiaiJ9 ) 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&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100156- sha1:ef05106 )___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-9926) Implement support for closed classification in SLDService Rasterizer
Mauro Bartolomeoli ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ae5899f77-4ce7-4c27-89f9-34256c006cb7 ) *created* an issue GeoServer ( https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiM2NjMTAzNzI4NWY1NDkwZWI4MjE0NWIyNWU4ODk0M2EiLCJwIjoiaiJ9 ) / Improvement ( https://osgeo-org.atlassian.net/browse/GEOS-9926?atlOrigin=eyJpIjoiM2NjMTAzNzI4NWY1NDkwZWI4MjE0NWIyNWU4ODk0M2EiLCJwIjoiaiJ9 ) GEOS-9926 ( https://osgeo-org.atlassian.net/browse/GEOS-9926?atlOrigin=eyJpIjoiM2NjMTAzNzI4NWY1NDkwZWI4MjE0NWIyNWU4ODk0M2EiLCJwIjoiaiJ9 ) Implement support for closed classification in SLDService Rasterizer ( https://osgeo-org.atlassian.net/browse/GEOS-9926?atlOrigin=eyJpIjoiM2NjMTAzNzI4NWY1NDkwZWI4MjE0NWIyNWU4ODk0M2EiLCJwIjoiaiJ9 ) Issue Type: Improvement Affects Versions: 2.18.2 Assignee: Unassigned Components: sldservice Created: 22/Feb/21 12:21 PM Priority: Medium Reporter: Mauro Bartolomeoli ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ae5899f77-4ce7-4c27-89f9-34256c006cb7 ) In the Rasterizer service we don't support a closed classification (where values outside of the configured min-max range should not be drawn). We should add a new flag (closed), false by default to enable closed classifications ( https://osgeo-org.atlassian.net/browse/GEOS-9926#add-comment?atlOrigin=eyJpIjoiM2NjMTAzNzI4NWY1NDkwZWI4MjE0NWIyNWU4ODk0M2EiLCJwIjoiaiJ9 ) Add Comment ( https://osgeo-org.atlassian.net/browse/GEOS-9926#add-comment?atlOrigin=eyJpIjoiM2NjMTAzNzI4NWY1NDkwZWI4MjE0NWIyNWU4ODk0M2EiLCJwIjoiaiJ9 ) 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&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100154- sha1:b810f81 )___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-9925) Update jai-ext to 1.1.20
Mauro Bartolomeoli ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ae5899f77-4ce7-4c27-89f9-34256c006cb7 ) *created* an issue GeoServer ( https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiZjNiYzEyMWM0YzY5NDAwZDhmNGJjOTBhNGY5MTcxMGYiLCJwIjoiaiJ9 ) / Improvement ( https://osgeo-org.atlassian.net/browse/GEOS-9925?atlOrigin=eyJpIjoiZjNiYzEyMWM0YzY5NDAwZDhmNGJjOTBhNGY5MTcxMGYiLCJwIjoiaiJ9 ) GEOS-9925 ( https://osgeo-org.atlassian.net/browse/GEOS-9925?atlOrigin=eyJpIjoiZjNiYzEyMWM0YzY5NDAwZDhmNGJjOTBhNGY5MTcxMGYiLCJwIjoiaiJ9 ) Update jai-ext to 1.1.20 ( https://osgeo-org.atlassian.net/browse/GEOS-9925?atlOrigin=eyJpIjoiZjNiYzEyMWM0YzY5NDAwZDhmNGJjOTBhNGY5MTcxMGYiLCJwIjoiaiJ9 ) Issue Type: Improvement Affects Versions: 2.18.2 Assignee: Mauro Bartolomeoli ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ae5899f77-4ce7-4c27-89f9-34256c006cb7 ) Components: WMS Created: 22/Feb/21 8:10 AM Priority: Medium Reporter: Mauro Bartolomeoli ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ae5899f77-4ce7-4c27-89f9-34256c006cb7 ) We should update jaiext to 1.1.20 to include this fix: https://github.com/geosolutions-it/jai-ext/issues/278 The fix is related to color encoding in paletted images ( https://osgeo-org.atlassian.net/browse/GEOS-9925#add-comment?atlOrigin=eyJpIjoiZjNiYzEyMWM0YzY5NDAwZDhmNGJjOTBhNGY5MTcxMGYiLCJwIjoiaiJ9 ) Add Comment ( https://osgeo-org.atlassian.net/browse/GEOS-9925#add-comment?atlOrigin=eyJpIjoiZjNiYzEyMWM0YzY5NDAwZDhmNGJjOTBhNGY5MTcxMGYiLCJwIjoiaiJ9 ) 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&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100154- sha1:b810f81 )___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-9873) Update jai-ext to 1.1.19
Mauro Bartolomeoli ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ae5899f77-4ce7-4c27-89f9-34256c006cb7 ) *created* an issue GeoServer ( https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiMDEyOWFlMjYxY2ZkNDJiZTg0Y2Q0MDI4NGVjMjc1YzQiLCJwIjoiaiJ9 ) / Improvement ( https://osgeo-org.atlassian.net/browse/GEOS-9873?atlOrigin=eyJpIjoiMDEyOWFlMjYxY2ZkNDJiZTg0Y2Q0MDI4NGVjMjc1YzQiLCJwIjoiaiJ9 ) GEOS-9873 ( https://osgeo-org.atlassian.net/browse/GEOS-9873?atlOrigin=eyJpIjoiMDEyOWFlMjYxY2ZkNDJiZTg0Y2Q0MDI4NGVjMjc1YzQiLCJwIjoiaiJ9 ) Update jai-ext to 1.1.19 ( https://osgeo-org.atlassian.net/browse/GEOS-9873?atlOrigin=eyJpIjoiMDEyOWFlMjYxY2ZkNDJiZTg0Y2Q0MDI4NGVjMjc1YzQiLCJwIjoiaiJ9 ) Issue Type: Improvement Affects Versions: 2.18.2 Assignee: Mauro Bartolomeoli ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ae5899f77-4ce7-4c27-89f9-34256c006cb7 ) Components: WMS Created: 26/Jan/21 8:37 AM Priority: Medium Reporter: Mauro Bartolomeoli ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Ae5899f77-4ce7-4c27-89f9-34256c006cb7 ) We should update jaiext to 1.1.19 to include this fix: https://github.com/geosolutions-it/jai-ext/issues/175 The fix is related to transparent color encoding in paletted images (e.g. PNG8) ( https://osgeo-org.atlassian.net/browse/GEOS-9873#add-comment?atlOrigin=eyJpIjoiMDEyOWFlMjYxY2ZkNDJiZTg0Y2Q0MDI4NGVjMjc1YzQiLCJwIjoiaiJ9 ) Add Comment ( https://osgeo-org.atlassian.net/browse/GEOS-9873#add-comment?atlOrigin=eyJpIjoiMDEyOWFlMjYxY2ZkNDJiZTg0Y2Q0MDI4NGVjMjc1YzQiLCJwIjoiaiJ9 ) 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&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100154- sha1:4dba4bb )___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Old jars and new maven repos
Hi Jody, thanks for your reply. We managed to publish on our maven repo from a local PC, updating the poms. I think it's enough for now. Mauro Il giorno ven 24 apr 2020 alle ore 23:05 Jody Garnett < jody.garn...@gmail.com> ha scritto: > You need to start building those yourself, or better yet upgrade to the most > recent stable release from that branch > <https://docs.geotools.org/latest/userguide/welcome/upgrade.html#upgrading-projects-using-historical-geotools-snapshots> > (as outlined in the geotools upgrade instructions). > > The snapshots are provided in part to collect feedback and contribute to > project sustainability. Having snapshots for builds that are no longer > active does not assist with this team goal. > > That said I am experimenting with a new setting for geotools artifacts > that will keep the last couple snapshots for any artifact. Initially the > repo was set to remove any snapshots after they went unused for a couple of > weeks. The previous boundless repository has been thrown out so the only > historical record of prior snapshots may be on your local .m2 repository. > > If you find it is mission critical to have snapshots for an archived > branch: > 1. The build jobs for the prior branches are still there > 2. Re-enable the job, remove the scheduling so it is just run manually > 3. Update the pom.xml publishing options on the branch, and rerun the > build on jenkins, or even run it on your local machine using your own osgeo > user id credentials in settings.xml. > > > > > On Thu, Apr 23, 2020 at 1:34 AM Mauro Bartolomeoli < > mauro.bartolome...@geo-solutions.it> wrote: > >> Hi, >> we noticed that on the new maven repos only jars from supported versions >> are available. >> So, GeoTools >= 22 and GeoServer >= 2.16. >> Internally we have some builds depending on 21.x and 2.15 stuff, so I was >> wondering if there is any plan to port those to the new repos or we need to >> start building those ourselves. >> >> -- >> >> Regards, >> >> Mauro Bartolomeoli >> >> == >> GeoServer Professional Services from the experts! Visit >> http://goo.gl/it488V for more information. >> == >> >> Dott. Mauro Bartolomeoli >> @mauro_bart >> Technical Lead >> >> GeoSolutions S.A.S. >> Via di Montramito 3/A >> <https://www.google.com/maps/search/Via+di+Montramito+3%2FA+55054+%C2%A0Massarosa+(LU)+Italy?entry=gmail&source=g> >> 55054 Massarosa (LU) >> <https://www.google.com/maps/search/Via+di+Montramito+3%2FA+55054+%C2%A0Massarosa+(LU)+Italy?entry=gmail&source=g> >> Italy >> <https://www.google.com/maps/search/Via+di+Montramito+3%2FA+55054+%C2%A0Massarosa+(LU)+Italy?entry=gmail&source=g> >> >> mobile: +39 393 904 1756 >> phone: +39 0584 962313 >> fax: +39 0584 1660272 >> >> http://www.geo-solutions.it >> http://twitter.com/geosolutions_it >> >> --- >> >> Con riferimento alla normativa sul trattamento dei dati personali (Reg. >> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si >> precisa che ogni circostanza inerente alla presente email (il suo >> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è >> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il >> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra >> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. >> >> This email is intended only for the person or entity to which it is >> addressed and may contain information that is privileged, confidential or >> otherwise protected from disclosure. We remind that - as provided by >> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this >> e-mail or the information herein by anyone other than the intended >> recipient is prohibited. If you have received this email by mistake, please >> notify us immediately by telephone or e-mail. >> ___ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> > -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --
[Geoserver-devel] Old jars and new maven repos
Hi, we noticed that on the new maven repos only jars from supported versions are available. So, GeoTools >= 22 and GeoServer >= 2.16. Internally we have some builds depending on 21.x and 2.15 stuff, so I was wondering if there is any plan to port those to the new repos or we need to start building those ourselves. -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-9539) URLKvpParser encodes urls also when not needed
Mauro Bartolomeoli ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A59ede444-77d6-4e81-b0f3-e8a269199530 ) *created* an issue GeoServer ( https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiNWQwMGVjYTI3MmQ5NDI5N2E5NzY0MTU2MTU3MTVlNjciLCJwIjoiaiJ9 ) / Bug ( https://osgeo-org.atlassian.net/browse/GEOS-9539?atlOrigin=eyJpIjoiNWQwMGVjYTI3MmQ5NDI5N2E5NzY0MTU2MTU3MTVlNjciLCJwIjoiaiJ9 ) GEOS-9539 ( https://osgeo-org.atlassian.net/browse/GEOS-9539?atlOrigin=eyJpIjoiNWQwMGVjYTI3MmQ5NDI5N2E5NzY0MTU2MTU3MTVlNjciLCJwIjoiaiJ9 ) URLKvpParser encodes urls also when not needed ( https://osgeo-org.atlassian.net/browse/GEOS-9539?atlOrigin=eyJpIjoiNWQwMGVjYTI3MmQ5NDI5N2E5NzY0MTU2MTU3MTVlNjciLCJwIjoiaiJ9 ) Issue Type: Bug Affects Versions: 2.17-RC Assignee: Unassigned Components: WMS Created: 13/Mar/20 6:23 PM Priority: Medium Reporter: Mauro Bartolomeoli ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A59ede444-77d6-4e81-b0f3-e8a269199530 ) URLKvpParser tries to fix wrong url by encoding them with an home-made algorithm, but sometimes this breaks perfectly valid urls. ( https://osgeo-org.atlassian.net/browse/GEOS-9539#add-comment?atlOrigin=eyJpIjoiNWQwMGVjYTI3MmQ5NDI5N2E5NzY0MTU2MTU3MTVlNjciLCJwIjoiaiJ9 ) Add Comment ( https://osgeo-org.atlassian.net/browse/GEOS-9539#add-comment?atlOrigin=eyJpIjoiNWQwMGVjYTI3MmQ5NDI5N2E5NzY0MTU2MTU3MTVlNjciLCJwIjoiaiJ9 ) 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&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100121- sha1:a2b3dcc )___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] GetFeatureInfo on raster with nodata
Hi, today I found that GetFeatureInfo on pixels with a nodata value returns the underlying pixel value (where a GetMap returns a transparent pixel). I would have expected (to be consistent with vector data behaviour) to have an empty recordset as the result. Talking with Daniele Romagnoli, I discovered that a parameter called EXCLUDE_NODATA_RESULT=true exists to return a different beast, the recordset is not empty but the real value is replaced with null. This is not working fully, indeed, because with an xml based output we get NaN and with json we get an error from the encoder. My question is: would be returning an empty recordset by default better in this case? Opinions are welcomed. -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-9444) SLDService raster classifier sets a wrong FeatureTypeName on produced SLD
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-9444 SLDService raster classifier sets a wrong FeatureTypeName on produced SLD Issue Type: Improvement Affects Versions: 2.16.1 Assignee: Mauro Bartolomeoli Components: sldservice Created: 07/Jan/20 4:11 PM Priority: Medium Reporter: Mauro Bartolomeoli SLD for rasters should either miss the FeatureTypeName definition in style, or use a Feature value for it. Raster classifier instead puts the layer name in it, so the produced SLD is not working. The fix is trivial. Add Comment
[Geoserver-devel] [JIRA] (GEOS-9427) Fix authkey regex examples for capturing username
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-9427 Fix authkey regex examples for capturing username Issue Type: Improvement Assignee: Mauro Bartolomeoli Components: authkey Created: 09/Dec/19 2:35 PM Fix Versions: 2.17-RC Priority: Medium Reporter: Mauro Bartolomeoli The regex for capturing user from a json document is wrong. Correct one should be something like: ^.?\"user\"\s:\s*\"([^\"]+)\".*$
Re: [Geoserver-devel] All committer please notice: cleanup in progress, please follow up with this mail ASAP (GSIP-180)
Hi Andrea, I am subscribed to all the 3 lists, and trying to participate as much as I can. Mauro Il giorno sab 26 ott 2019 alle ore 11:47 Andrea Aime < andrea.a...@geo-solutions.it> ha scritto: > Hi, > as per GSIP-180 I'm cleaning up the list of GeoServer committers. Phase > one, removing the developers > that have not been active in the last year, has been done. > > Now it's time to proceed to phase two, check that all remaining committers > are participating to the > community, and are subscribed to the devel, build and user lists. > I have prepared a spreadsheet with the current list of committers and > their list status here (accessible read only): > > https://docs.google.com/spreadsheets/d/18wWH9pTcKDdZaVOK3N8W4po01VprO3e9n08ihEELdIs/edit#gid=0 > > I cannot access the list rosters anymore (GPDR I presume) so please reply > to this thread confirming your mail list > subscription status. > I'll wait two weeks, and then remove commit access from anyone that did > not respond to this mail, or those > that answered but are unwilling to take part on the lists. > > If anyone failed to see the message due to a vacation, work trip, and > whatever other reason, > and got removed, no worries, we will happily reinstate access once you > comply with the community participation :-D > > I remind you that being committer is not a requirement for general > community participation, it just allows > direct commit, PR merge rights, wiki editing (including GSIP writing) > and allows for release management. Other activities like PSC participation > are still possible, and code contributions > are still possible via pull requests. > > If you read this mail and don't see your name in the list above, but need > commit rights to maintain a community > module or similar activities, also please let us know. > > Cheers > Andrea > > == GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf > Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa > (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 > http://www.geo-solutions.it http://twitter.com/geosolutions_it > --- *Con riferimento > alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - > Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni > circostanza inerente alla presente email (il suo contenuto, gli eventuali > allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i > destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per > errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le > sarei comunque grato se potesse darmene notizia. This email is intended > only for the person or entity to which it is addressed and may contain > information that is privileged, confidential or otherwise protected from > disclosure. We remind that - as provided by European Regulation 2016/679 > “GDPR” - copying, dissemination or use of this e-mail or the information > herein by anyone other than the intended recipient is prohibited. If you > have received this email by mistake, please notify us immediately by > telephone or e-mail.* > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited.
[Geoserver-devel] [JIRA] (GEOS-9355) Allow using params-extractor filter to act before security chain
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-9355 Allow using params-extractor filter to act before security chain Issue Type: Improvement Affects Versions: 2.16.0 Assignee: Mauro Bartolomeoli Components: params-extractor Created: 02/Oct/19 12:16 PM Priority: Medium Reporter: Mauro Bartolomeoli Currently params-extractor filter is initialized as a spring filter, so it runs after the security chain. If we allow the filter to be used as a standard servlet filter, it would also affect the security filter chain (allowing for example params extraction for the authkey module) Add Comment
Re: [Geoserver-devel] Enabling params-extractor usage as a standard filter in web.xml
Hi Andrea, I did some tests and it looks to be working fine. I can eventually add some code to avoid it (since init is only called if configured in web.xml I can probably put some code there to make the spring duplicate "not working") I will do more testing before preparing a PR. Mauro Il giorno mer 25 set 2019 alle ore 10:30 Andrea Aime < andrea.a...@geo-solutions.it> ha scritto: > Hi Mauro, > if configured in the web.xml, it would also be picked from the application > context or not? > If so it would run twice, is that a problem? > > Cheers > Andrea > > > On Tue, Sep 24, 2019 at 3:54 PM Mauro Bartolomeoli < > mauro.bartolome...@geo-solutions.it> wrote: > >> Good afternoon, >> as you may know, the params-extractor community module can be used in >> GeoServer to transform url path fragments to normal query string parameters >> ( >> https://docs.geoserver.org/latest/en/user/community/params-extractor/index.html >> ). >> This is working fine except for one use-case that we need to cover for >> one customer: the ability to use it together with the authkey >> authentication filter. >> Long story short, we would like to implement the ability to express the >> authkey as part of the url path (e.g. /geoserver/!@/wms) and this >> would be a perfect fit for the params-extractor module, but unfortunately >> security filters run before spring configured filters (and params-extractor >> is a spring configured filter in GeoServer). >> >> We found a possible solution, that requires registering the same filter >> in tomcat web.xml, so that it can run before the usual timing. Being able >> to do so requires only a couple of changes: >> * adding an empty constructor to the filter >> * adding code in the init method of the filter to initialize config when >> run through web.xml >> >> Obviously the filter could be used the old way, or the new way, just by >> registering it in the tomcat web.xml or not. >> >> Any alternative idea? >> >> -- >> >> Regards, >> >> Mauro Bartolomeoli >> >> == >> GeoServer Professional Services from the experts! Visit >> http://goo.gl/it488V for more information. >> == >> >> Dott. Mauro Bartolomeoli >> @mauro_bart >> Technical Lead >> >> GeoSolutions S.A.S. >> Via di Montramito 3/A >> 55054 Massarosa (LU) >> Italy >> >> mobile: +39 393 904 1756 >> phone: +39 0584 962313 >> fax: +39 0584 1660272 >> >> http://www.geo-solutions.it >> http://twitter.com/geosolutions_it >> >> --- >> >> Con riferimento alla normativa sul trattamento dei dati personali (Reg. >> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si >> precisa che ogni circostanza inerente alla presente email (il suo >> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è >> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il >> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra >> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. >> >> This email is intended only for the person or entity to which it is >> addressed and may contain information that is privileged, confidential or >> otherwise protected from disclosure. We remind that - as provided by >> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this >> e-mail or the information herein by anyone other than the intended >> recipient is prohibited. If you have received this email by mistake, please >> notify us immediately by telephone or e-mail. >> >> ___ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> > > > -- > > Regards, Andrea Aime == GeoServer Professional Services from the experts! > Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime > @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 > Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 > 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it > --- *Con riferimento > alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - > Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni > circostanza inerente alla presente email (il suo contenuto, gli eventuali > allegati, etc.) è un dato la cui conoscenza
[Geoserver-devel] Enabling params-extractor usage as a standard filter in web.xml
Good afternoon, as you may know, the params-extractor community module can be used in GeoServer to transform url path fragments to normal query string parameters ( https://docs.geoserver.org/latest/en/user/community/params-extractor/index.html ). This is working fine except for one use-case that we need to cover for one customer: the ability to use it together with the authkey authentication filter. Long story short, we would like to implement the ability to express the authkey as part of the url path (e.g. /geoserver/!@/wms) and this would be a perfect fit for the params-extractor module, but unfortunately security filters run before spring configured filters (and params-extractor is a spring configured filter in GeoServer). We found a possible solution, that requires registering the same filter in tomcat web.xml, so that it can run before the usual timing. Being able to do so requires only a couple of changes: * adding an empty constructor to the filter * adding code in the init method of the filter to initialize config when run through web.xml Obviously the filter could be used the old way, or the new way, just by registering it in the tomcat web.xml or not. Any alternative idea? -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Backporting GEOS-9255 (authkey promotion to extension)
Hi, I would like to backport extension status of the authkey module to 2.15.x. The related pull request is here: https://github.com/geoserver/geoserver/pull/3701 Any concern, objections? Mauro -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Backporting GEOS-9239 to 2.15.x
Hi, I would like to backport the WMS optional flags to remove root Layer in Capabilities documents. When the flags are not set the default is to use the old behaviour (always add a root Layer), so it should be safe to backport. Any concern? -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Promoting authkey community module to extension
And here is the PR: https://github.com/geoserver/geoserver/pull/3609 Il giorno mar 18 giu 2019 alle ore 18:56 Nuno Oliveira < nuno.olive...@geo-solutions.it> ha scritto: > +1 (non PSC member), is a quite useful module :) > > On Tue, 2019-06-18 at 09:26 +0200, Mauro Bartolomeoli wrote: > > Here it is: https://github.com/geoserver/geoserver/wiki/GSIP-174 > > Please, kindly, vote. > > Il giorno mar 18 giu 2019 alle ore 08:13 Andrea Aime < > andrea.a...@geo-solutions.it> ha scritto: > > On Tue, Jun 18, 2019 at 8:13 AM Andrea Aime > wrote: > > Hi Mauro, > +1, please proceed with PR. > > > Sigh, not enough coffee yet... please proceed with GSIP :-D > > Cheers > Andrea > > == > > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf > Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa > (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 > http://www.geo-solutions.it http://twitter.com/geosolutions_it > --- *Con riferimento > alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - > Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni > circostanza inerente alla presente email (il suo contenuto, gli eventuali > allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i > destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per > errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le > sarei comunque grato se potesse darmene notizia. This email is intended > only for the person or entity to which it is addressed and may contain > information that is privileged, confidential or otherwise protected from > disclosure. We remind that - as provided by European Regulation 2016/679 > “GDPR” - copying, dissemination or use of this e-mail or the information > herein by anyone other than the intended recipient is prohibited. If you > have received this email by mistake, please notify us immediately by > telephone or e-mail.* > > > > -- > > Regards, > > Mauro Bartolomeoli > > == > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. > == > > Dott. Mauro Bartolomeoli > @mauro_bart > Technical Lead > > GeoSolutions S.A.S. > Via di Montramito 3/A > 55054 Massarosa (LU) > Italy > > mobile: +39 393 904 1756 > phone: +39 0584 962313 > fax: +39 0584 1660272 > > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > > --- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail. > > ___ > Geoserver-devel mailing > listGeoserver-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/geoserver-devel > > -- > Regards, > Nuno Oliveira > == > GeoServer Professional Services from the > experts! > Visit http://goo.gl/it488V for more information. > == > > Nuno Miguel Carvalho Oliveira > @nmcoliveira > Software Engineer > > GeoSolutions S.A.S. > Via di Montramito 3/A > 55054 Massarosa (LU) > Italy > phone: +39 0584 962313 > fax: +39 0584 1660272 > http://www.geo-solutions.ithttp://twitter.com/geosolutions_it > > --- > > Con riferimento alla normativa sul trattamento dei dati > personali (Reg. UE 2016/679 - Regolamento generale sulla > protezione dei dati “GDPR”), si precisa che ogni > circostanza inerente alla presente email (il suo contenuto, > gli eventuali allegati, etc.) è un dato la cui conoscenza > è riservata al/i solo/i destinatario/i in
[Geoserver-devel] [JIRA] (GEOS-9264) GWC module include properties that belong to the GWC-S3 community module
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-9264 GWC module include properties that belong to the GWC-S3 community module Issue Type: Improvement Affects Versions: 2.15.1 Assignee: Mauro Bartolomeoli Components: GWC Created: 24/Jun/19 9:37 AM Priority: Medium Reporter: Mauro Bartolomeoli Messages for the GWC-S3 configuration panel are wrongly included in the core GWC GeoServerApplication.properties file. We should move them to the GWC-S3 community module resources. Add Comment
[Geoserver-devel] [JIRA] (GEOS-9259) Rename onelogin plugin to saml and improve compatibility
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-9259 Rename onelogin plugin to saml and improve compatibility Issue Type: Improvement Affects Versions: 2.15.1 Assignee: Mauro Bartolomeoli Components: onelogin Created: 19/Jun/19 6:02 PM Priority: Medium Reporter: Mauro Bartolomeoli We want to improve the actual onelogin community module to make it a more generic SAMlv2 authentication module, adding more configuration options such as: support for a local metadata xml in addition to the remote endpoint add the ability to sign requests Add Comment
[Geoserver-devel] [JIRA] (GEOS-9256) Parameter Extractor plugin cannot mangle URL correctly if Monitor plugin is installed
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-9256 Parameter Extractor plugin cannot mangle URL correctly if Monitor plugin is installed Issue Type: Bug Affects Versions: 2.15.1 Assignee: Mauro Bartolomeoli Components: params-extractor Created: 18/Jun/19 12:41 PM Priority: Medium Reporter: Mauro Bartolomeoli the Monitor plugin wraps the original request but does not use a RequestWrapper, it uses an HttpServletRequestWrapper, so the params extractor module is not able to correctly unwrap the original request. Add Comment
Re: [Geoserver-devel] Promoting authkey community module to extension
Here it is: https://github.com/geoserver/geoserver/wiki/GSIP-174 Please, kindly, vote. Il giorno mar 18 giu 2019 alle ore 08:13 Andrea Aime < andrea.a...@geo-solutions.it> ha scritto: > On Tue, Jun 18, 2019 at 8:13 AM Andrea Aime > wrote: > >> Hi Mauro, >> +1, please proceed with PR. >> > > Sigh, not enough coffee yet... please proceed with GSIP :-D > > Cheers > Andrea > > == > > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf > Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa > (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 > http://www.geo-solutions.it http://twitter.com/geosolutions_it > --- *Con riferimento > alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - > Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni > circostanza inerente alla presente email (il suo contenuto, gli eventuali > allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i > destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per > errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le > sarei comunque grato se potesse darmene notizia. This email is intended > only for the person or entity to which it is addressed and may contain > information that is privileged, confidential or otherwise protected from > disclosure. We remind that - as provided by European Regulation 2016/679 > “GDPR” - copying, dissemination or use of this e-mail or the information > herein by anyone other than the intended recipient is prohibited. If you > have received this email by mistake, please notify us immediately by > telephone or e-mail.* > -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-9255) Promote authkey to extension (GSIP-174)
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-9255 Promote authkey to extension (GSIP-174) Issue Type: Improvement Affects Versions: 2.15.1 Assignee: Mauro Bartolomeoli Components: authkey Created: 18/Jun/19 9:25 AM Priority: Medium Reporter: Mauro Bartolomeoli GSIP at https://github.com/geoserver/geoserver/wiki/GSIP-174 Add Comment
[Geoserver-devel] Promoting authkey community module to extension
Hi, I would like to ask for promotion of the authkey module to extension status. Some of the requirements for promotion: - [x] The module have at least a "handful" of users: since we added the ability to use an external validation service, the module has been used to integrate security between geoserver and external application in a lot of cases. - [x] The module have a designated and active maintainer: I contributed several improvements in the last years, and would like to become the mantainer of the module. - [ ] The module is considered "stable" by the majority of the PSC. - [x] The module maintain 40% test coverage: (about 55% with Jacoco) - [x] The modules have no IP violations. - [x] The module has a page in the user manual: https://docs.geoserver.org/stable/en/user/community/authkey/index.html - [x] The maintainer (Mauro Bartolomeoli) has signed the GeoServer Contributor Agreement, also as a maintaner of other GeoServer features (WMTS cascading). If no objection arise, I would proceed creating a GSIP for this. -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-9239) Options to return WMS Capabilities document without a root Layer tag, when possible
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-9239 Options to return WMS Capabilities document without a root Layer tag, when possible Issue Type: Improvement Affects Versions: 2.15.1 Assignee: Mauro Bartolomeoli Components: WMS Created: 06/Jun/19 5:31 PM Priority: Medium Reporter: Mauro Bartolomeoli We want to let the admin configure the ability to return WMS capabilities document without the usual root Layer when that is possible, so when there is only one Layer element as its child, for example when asking for a virtual service capabilities for a single layer or layergroup. The options should be configurable at the service (WMS) level, but also at the Layer / LayerGroup level. We could also add a vendor parameter to enable this new behaviour per user request. Add Comment
[Geoserver-devel] Backporting GEOS-9193 to 2.15
Hi, I would like to ask if there are any objections on backporting GEOS-9193 (made a private method protected in HTMLFeatureInfoOutputFormat to ease reuse in extended classes) to 2.15.x and eventually 2.14.x -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-9229) SLD file renamed with REST PUT request when not needed
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-9229 SLD file renamed with REST PUT request when not needed Issue Type: Bug Assignee: Unassigned Components: REST Created: 24/May/19 11:59 AM Priority: Medium Reporter: Mauro Bartolomeoli When a REST PUT request to modify a style contains the name of the style, the underlying SLD file is renamed also if the name is not changed, moreover the XML will still use to the old name. We should rename the resource only if the old name and the new one are not identical. Add Comment
Re: [Geoserver-devel] Optional flag to remove root Layer in WMS Capabilities documents
Hi Jody. The most interesting use case is when you are asking for a layer group and you get the group as root and the subgroups and layers as child nodes (so not really a single layer, but a tree with a single root, that is not the GS default root, but the group itself). I would not make it active by default, because I suspect many GeoServer aware WMS clients could stop working. Mauro Il mar 21 mag 2019, 00:47 Jody Garnett ha scritto: > No objection to the idea, it is just very unusual to see a WMS service > configured this way (with a single layer). That said, is there any reason > not to do this *all* the time for the cases you mention (layer group and > single layer)? If it really is unnecessary > -- > Jody Garnett > > > On Mon, 20 May 2019 at 06:01, Mauro Bartolomeoli < > mauro.bartolome...@geo-solutions.it> wrote: > >> Hi, >> to improve compatibility with some WMS clients, we would like to add an >> option for WMS to produce capabilities documents without the root layer tag >> when this is not necessary (e.g. when you ask for a virtual service, either >> a layergroup or a single layer, and thus you already have a single root, >> the group or the single layer). >> This could be implemented as a global / virtual service configuration, as >> a query string parameter or both. >> >> Any thought / objection? >> >> -- >> >> Regards, >> >> Mauro Bartolomeoli >> >> == >> GeoServer Professional Services from the experts! Visit >> http://goo.gl/it488V for more information. >> == >> >> Dott. Mauro Bartolomeoli >> @mauro_bart >> Technical Lead >> >> GeoSolutions S.A.S. >> Via di Montramito 3/A >> 55054 Massarosa (LU) >> Italy >> >> mobile: +39 393 904 1756 >> phone: +39 0584 962313 >> fax: +39 0584 1660272 >> >> http://www.geo-solutions.it >> http://twitter.com/geosolutions_it >> >> --- >> >> Con riferimento alla normativa sul trattamento dei dati personali (Reg. >> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si >> precisa che ogni circostanza inerente alla presente email (il suo >> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è >> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il >> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra >> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. >> >> This email is intended only for the person or entity to which it is >> addressed and may contain information that is privileged, confidential or >> otherwise protected from disclosure. We remind that - as provided by >> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this >> e-mail or the information herein by anyone other than the intended >> recipient is prohibited. If you have received this email by mistake, please >> notify us immediately by telephone or e-mail. >> >> ___ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Optional flag to remove root Layer in WMS Capabilities documents
Hi, to improve compatibility with some WMS clients, we would like to add an option for WMS to produce capabilities documents without the root layer tag when this is not necessary (e.g. when you ask for a virtual service, either a layergroup or a single layer, and thus you already have a single root, the group or the single layer). This could be implemented as a global / virtual service configuration, as a query string parameter or both. Any thought / objection? -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] OneLogin community module
Hi, we are starting some work to improve the onelogin community module. The basic idea is to improve its configurability to transform it into a more generic SAMLv2 SSO module. First idea: should we rename the module to something like samlv2? Is there any project rule / concern on renaming existing community modules? -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-9208) SLDService raster classifier updates layer default style by mistake
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-9208 SLDService raster classifier updates layer default style by mistake Issue Type: Bug Affects Versions: 2.15.1 Assignee: Mauro Bartolomeoli Components: sldservice Created: 10/May/19 3:41 PM Priority: High Reporter: Mauro Bartolomeoli Instead of creating / returning a new style, the raster classifier changes the layer default style in memory, so the latest classification is used until geoserver is reloaded / restarted. We should create a new style object every time instead. Add Comment
[Geoserver-devel] [JIRA] (GEOS-9200) Add support for configuring ACL in gwc-s3 community module
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-9200 Add support for configuring ACL in gwc-s3 community module Issue Type: Improvement Affects Versions: 2.15.1 Assignee: Mauro Bartolomeoli Components: GWC-S3 Created: 03/May/19 4:13 PM Priority: Medium Reporter: Mauro Bartolomeoli Current geowebcache supports configuring S3 permissions on newly created files, but no UI option is available in the BlobStore configuration page. We should add that, so that private access can be used (currently all files are created as public). Add Comment
[Geoserver-devel] [JIRA] (GEOS-9197) Add repeatable params to params-extractor community module
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-9197 Add repeatable params to params-extractor community module Issue Type: Improvement Affects Versions: 2.15.1 Assignee: Mauro Bartolomeoli Created: 03/May/19 3:41 PM Priority: Medium Reporter: Mauro Bartolomeoli We want to add the ability to have params that can be "replicated" for every layer in the request. This is useful for params like styles or filter that need a value for each specified layer. A
[Geoserver-devel] [JIRA] (GEOS-9198) Add support for env parameters in authkey community module configuration (expecially for webservice url)
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-9198 Add support for env parameters in authkey community module configuration (expecially for webservice url) Issue Type: Improvement Affects Versions: 2.15.1 Assignee: Unassigned Components: authkey Created: 03/May/19 3:45 PM Priority: Medium Reporter: Mauro Bartolomeoli Currently env parameters in configuration is supported for catalog and some specific modules / plugins. We want to add support to the authkey module (e.g. to support different authkey webservice hosts in different environments) Add Comment
[Geoserver-devel] [JIRA] (GEOS-9193) Make HTMLFeatureInfoOutputFormat getTemplate method protected
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-9193 Make HTMLFeatureInfoOutputFormat getTemplate method protected Issue Type: Improvement Affects Versions: 2.15.1 Assignee: Mauro Bartolomeoli Components: WMS Created: 30/Apr/19 6:10 PM Fix Versions: 2.16-RC Priority: Medium Reporter: Mauro Bartolomeoli This would allow extending the class and reusing the template loading logic. Add Comment
[Geoserver-devel] HTMLFeatureInfoOutputFormat getTemplate method visibility
I would like to transform the method visibility to protected (currently package private) , so that I can reuse it in an extended class. Any objection? -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-9137) Add WMS configuration options for densification on reprojection and disabling wrapping dateline heuristic
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-9137 Add WMS configuration options for densification on reprojection and disabling wrapping dateline heuristic Issue Type: Improvement Affects Versions: 2.15.0 Assignee: Mauro Bartolomeoli Components: WMS Created: 05/Mar/19 11:13 AM Priority: Medium Reporter: Mauro Bartolomeoli GEOT-6255 Open andGEOT-6257 Open add support for new options when advanced projection handling is enabled: automatic geometry densification for better reprojection results disabling dateline wrapping heuristic that can give wrong results with some data We want these options to be configurable via WMS admin page. Add
Re: [Geoserver-devel] Some new options for WMS advanced projection handling
Hi all, I started working on this, and produced a first PR for GeoTools: https://github.com/geotools/geotools/pull/2285 Please, let me know your feedbacks. Il giorno mer 6 feb 2019 alle ore 12:53 Andrea Aime < andrea.a...@geo-solutions.it> ha scritto: > On Wed, Feb 6, 2019 at 12:06 PM Mauro Bartolomeoli < > mauro.bartolome...@geo-solutions.it> wrote: > >> Hi, I would like to add some optional behaviours for the >> advanced projection handling module, in particular: >> >> * ability to disable the dateline crossing heuristic in >> WrappingProjectionHandler (sometimes it creates weird polygons, because of >> wrong assumptions, but it cannot be actually disabled without disabling >> wrapping completely) >> > > I'd rather try to fix the heuristics, but yes, as an heuristic, it's never > going to be 100% correct. A flag to disable it might be interesting, > although, it's going to get hairy to decide when and how to do so. > A simple setup might be to have it global, like the wrapping now, > controlled by a StreamingRenderer hint like the > exiting CONTINUOUS_MAP_WRAPPING (see below) > > >> * ability to densify points before reprojection; the densification >> distance should be configurable too (both for metric and degrees source >> CRSs); this would allow "deforming" projections to have more precise >> reprojections, with a (hopefully) small performance loss. Every projection >> handler should be able to decide if densification makes sense or not for >> that projection. I would use JTS Densifier for the job. >> > > This was being discussed only a few days ago, see the "Misaligned layers > after reprojecting with on-the-fly geometry simplification" thread. > The crux of the issue is that the amount of densification required to get > a smooth looking output is dynamic, and depends on a variety of factors: > >- the current area involved in the reprojection (close or far away >from the central meridians?) >- the zoom level (curved lines only normally need to appear when >looking at wide areas) >- the overall reprojection involved, e.g., if I have a straight line >defined in polar stereographic coordinates, and want to display in UTM, the >polar stereo will bend the line in one way to make it go WGS84, and the UTM >in a different way > > Thankfully we already have machinery to evaluate the amount of non linear > deformation involved in a certain reprojection in a certain area, we use to > to figure out if we can use an equivalent AffineTransform, or a regular > grid of AffineTransforms over the area, when reprojecting rasters, here: > > https://github.com/geotools/geotools/blob/master/modules/library/referencing/src/main/java/org/geotools/referencing/operation/transform/WarpBuilder.java > I have the beginning of some changes to that class that would allow to > determine in how many subsets to split the drawing area in order to > consider each subset linear: > https://github.com/aaime/geotools/commits/dynamic_densify > In other words, if the tool tells you you have to split the rendering area > in a 10x10 grid, and the rendering area is 1024x768, then you could add a > point every 768/10 pixels in the data, and the result would look smooth > enough (and if it's 1x1, then you'd have not to densify at all). > You'd still have to determine what that means in terms of source CRS > distances, but that should not be too hard I hope. > > Using the JTS Densifier may cause performance issues, JTS has the bad > habit of turning our optimized LiteCoordinateSequence into > CoordinateArraySequence, which allocates a bazillion objects to just > represent a line... however, one could first ask if the densification is > needed by looking at the bbox of the geometry, if it's smaller than the > densification distance, then you can skip it, leaving the overhead only to > those bits that actually need to be densified. > > >> The first concern, is where to store those options if we want them to be >> configurable from the UI (In an initial prototype I am using system >> properties, but I would like something more user friendly). Maybe we can >> add a new parameter to the ProjectionHandlerFactory: a map of hints / >> options that projection handlers can use to configure themselves. This >> would allow introducing new options in the future without extending the >> interface again. >> > > It would, but pay attention not to break backwards compatibility, the > easiest thing is to add a new method and deprecate the old one, the old one > would refer to the new by using an empty map, or if you put wrapping in > int, turning
[Geoserver-devel] Some new options for WMS advanced projection handling
Hi, I would like to add some optional behaviours for the advanced projection handling module, in particular: * ability to disable the dateline crossing heuristic in WrappingProjectionHandler (sometimes it creates weird polygons, because of wrong assumptions, but it cannot be actually disabled without disabling wrapping completely) * ability to densify points before reprojection; the densification distance should be configurable too (both for metric and degrees source CRSs); this would allow "deforming" projections to have more precise reprojections, with a (hopefully) small performance loss. Every projection handler should be able to decide if densification makes sense or not for that projection. I would use JTS Densifier for the job. The first concern, is where to store those options if we want them to be configurable from the UI (In an initial prototype I am using system properties, but I would like something more user friendly). Maybe we can add a new parameter to the ProjectionHandlerFactory: a map of hints / options that projection handlers can use to configure themselves. This would allow introducing new options in the future without extending the interface again. Thoughts? Concerns? -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] LDAP tests and JDK11
Hi, I did some investigation on updating our LDAP test infrastructure to be compatible with JDK11. The main obstacle is the embedded LDAP server (apacheds) we use for testing. The current one uses some deprecated classes sun.*, so I tried upgrading to a newer version. I found that 2.0.0-Mxx versions (there is no 2.0.0 final version yet) are compatible, but unfortunately tests execution times are not comparable (4-5 times slower), even with JDK8. I don't think it's acceptable to have tests so slow to execute (40-50 seconds for each unit test), so unless we find a way to speed-up apacheds start time, or migrate to a different testing solution, I would leave the code untouched for now. I pushed my work on branch of my fork: https://github.com/mbarto/geoserver/tree/jdk11_ldap_test -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Backporting WFS coordinates formatting options for complex features
Hi, any objection if we backport this one: https://github.com/geoserver/geoserver/pull/3212 to 2.14.x? It is an addition to GEOT-6119 and GEOS-8935 work that added new formatting options for coordinates in WFS / GML formats. This one allows formatting options to work also for complex features. -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Backporting GEOT-6119 to GT 20.x and related GEOS-8935 to GS 2.14.x
Hi, any objections if I backport WFS coordinates formatting new options to 20.x / 2.14.x versions? -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Backporting GEOS-8827
Any concern in backporting https://osgeo-org.atlassian.net/browse/GEOS-8827 to 2.14.x ? It introduces optional caching of styles fetched through the WMS SLD parameter. Thanks -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-8935) Introduce new coordinates formatting options for WFS layers
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-8935 Introduce new coordinates formatting options for WFS layers Issue Type: Improvement Affects Versions: 2.14-RC Assignee: Mauro Bartolomeoli Components: WFS Created: 17/Sep/18 11:16 AM Priority: Medium Reporter: Mauro Bartolomeoli Using https://osgeo-org.atlassian.net/browse/GEOT-6119 we would like to introduce two new options for WFS layers, related to coordinates formatting in GML: allow / deny scientific notation force right-zero padding up to configured # of decimals Add Comment
Re: [Geoserver-devel] [Geotools-devel] New coordinates formatting options for WFS
Hi Andrea, Il giorno ven 14 set 2018 alle ore 12:44 Andrea Aime < andrea.a...@geo-solutions.it> ha scritto: > Hi Mauro, > no concerns on having the extra options, just mind, the class in question > has been written in place of using > a DecimalFormat because the latter was significantly slowing down writing > performance, so make sure the > extra options do not add slowdowns, or do so only when activated. > Yes, I already have the geotools part mostly working, and since forceDecimal was already there, I only added a zero padding option that runs extra code only when active, so it should not affect existing implementation. -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] New coordinates formatting options for WFS
Hi, I was asked to improve formatting options for coordinates in WFS output. Currently we only have the ability to set the max # of decimals. We would like to introduce some new options, in particular: - force use of decimals notation, disallowing scientific notation - introduce optional zero (right-)padding for decimals, up to configured # of decimals To implement that I would: - improve the existing GeoTools CoordinateFormatter (force decimal encoding is already there, we only need a padWithZeros option) - introduce new options (forceDecimal and padWithZeros) where needed (GMLWriter, GML configurations, etc.), leaving the default behaviour untouched - introduce the new options in GeoServer FeatureType / Layer configurations and related UI Any concern / advice? -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Promoting SLDservice community module to extension
If there are no objections, I would merge it, I think we have enough votes to go. Mauro Il giorno mar 21 ago 2018 alle ore 10:53 Mauro Bartolomeoli < mauro.bartolome...@geo-solutions.it> ha scritto: > Hi, > the PR for this one is ready: > https://github.com/geoserver/geoserver/pull/3062 > > Il giorno mar 7 ago 2018 alle ore 18:43 Kevin Smith > ha scritto: > >> +1 >> >> On 2018-08-01 10:13 PM, Andrea Aime wrote: >> >> Yep, it's a GSIP vote :) >> >> Ah, +1 here too >> >> Cheers >> Andrea >> >> >> On Thu, Aug 2, 2018 at 6:16 AM wrote: >> >>> I’m +0 on this. Are you actually looking for votes on the GSIP at this >>> time? >>> >>> >>> >>> Brad >>> >>> >>> >>> *From:* Mauro Bartolomeoli >>> *Sent:* Wednesday, 1 August 2018 1:12 AM >>> *To:* Geoserver-devel >>> *Subject:* Re: [Geoserver-devel] Promoting SLDservice community module >>> to extension >>> >>> >>> >>> GSIP is here: https://github.com/geoserver/geoserver/wiki/GSIP-170 >>> >>> >>> >>> Mauro >>> >>> >>> >>> >>> >>> Il giorno dom 29 lug 2018 alle ore 22:05 Andrea Aime < >>> andrea.a...@geo-solutions.it> ha scritto: >>> >>> Gsssipit! >>> >>> >>> >>> Cheers >>> >>> Andrea >>> >>> >>> >>> Il Ven 27 Lug 2018, 19:21 Mauro Bartolomeoli < >>> mauro.bartolome...@geo-solutions.it> ha scritto: >>> >>> Hi, I would like to propose SLDservice promotion to extension. >>> >>> >>> >>> Some of the requirements for promotion: >>> >>> >>> >>> - [x] The modules have at least a "handful" of users: recent interest in >>> improvements to the module show that some people are using it. >>> >>> - [x] The modules have a designated and active maintainer: I contributed >>> several improvements recently, and would like to become the mantainer of >>> the module. >>> >>> - [ ] The modules are considered "stable" by the majority of the PSC. >>> >>> - [x] The modules maintain 40% test coverage: (about 41% with Jacoco) >>> >>> - [x] The modules have no IP violations. >>> >>> - [x] The module has a page in the user manual: >>> >>> - [x] The maintainer (Mauro Bartolomeoli) has signed the GeoServer >>> Contributor Agreement, also as a maintaner of other GeoServer features >>> (WMTS cascading). >>> >>> >>> >>> If no objection arise, I would proceed creating a GSIP for this. >>> >>> >>> >>> -- >>> >>> Regards, >>> >>> Mauro Bartolomeoli >>> >>> == >>> GeoServer Professional Services from the experts! Visit >>> http://goo.gl/it488V for more information. >>> == >>> >>> Dott. Mauro Bartolomeoli >>> @mauro_bart >>> Technical Lead >>> >>> GeoSolutions S.A.S. >>> Via di Montramito 3/A >>> 55054 Massarosa (LU) >>> Italy >>> >>> mobile: +39 393 904 1756 >>> phone: +39 0584 962313 >>> fax: +39 0584 1660272 >>> >>> http://www.geo-solutions.it >>> http://twitter.com/geosolutions_it >>> >>> --- >>> >>> >>> >>> *Con riferimento alla normativa sul trattamento dei dati personali (Reg. >>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si >>> precisa che ogni circostanza inerente alla presente email (il suo >>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è >>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il >>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra >>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. >>> This email is intended only for the person or entity to which it is >>> addressed and may contain information that is privileged, confidential or >>> otherwise protected from disclosure. We remind that - as provided by >>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this >>> e-mail or the information herein by anyone other than the intended >>> recipient is prohibited. If you hav
[Geoserver-devel] [JIRA] (GEOS-8903) Introduce expression support in RasterSymbolizer GammaValue
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-8903 Introduce _expression_ support in RasterSymbolizer GammaValue Issue Type: Improvement Affects Versions: 2.14-RC Assignee: Mauro Bartolomeoli Components: styling Created: 22/Aug/18 2:08 PM Priority: Medium Reporter: Mauro Bartolomeoli In particular to support env variables, but not limited to that. Currently only some attributes / elements support values as expressions. We would like to introduce support for GammaValue. Add Comment
Re: [Geoserver-devel] Promoting SLDservice community module to extension
Hi, the PR for this one is ready: https://github.com/geoserver/geoserver/pull/3062 Il giorno mar 7 ago 2018 alle ore 18:43 Kevin Smith ha scritto: > +1 > > On 2018-08-01 10:13 PM, Andrea Aime wrote: > > Yep, it's a GSIP vote :) > > Ah, +1 here too > > Cheers > Andrea > > > On Thu, Aug 2, 2018 at 6:16 AM wrote: > >> I’m +0 on this. Are you actually looking for votes on the GSIP at this >> time? >> >> >> >> Brad >> >> >> >> *From:* Mauro Bartolomeoli >> *Sent:* Wednesday, 1 August 2018 1:12 AM >> *To:* Geoserver-devel >> *Subject:* Re: [Geoserver-devel] Promoting SLDservice community module >> to extension >> >> >> >> GSIP is here: https://github.com/geoserver/geoserver/wiki/GSIP-170 >> >> >> >> Mauro >> >> >> >> >> >> Il giorno dom 29 lug 2018 alle ore 22:05 Andrea Aime < >> andrea.a...@geo-solutions.it> ha scritto: >> >> Gsssipit! >> >> >> >> Cheers >> >> Andrea >> >> >> >> Il Ven 27 Lug 2018, 19:21 Mauro Bartolomeoli < >> mauro.bartolome...@geo-solutions.it> ha scritto: >> >> Hi, I would like to propose SLDservice promotion to extension. >> >> >> >> Some of the requirements for promotion: >> >> >> >> - [x] The modules have at least a "handful" of users: recent interest in >> improvements to the module show that some people are using it. >> >> - [x] The modules have a designated and active maintainer: I contributed >> several improvements recently, and would like to become the mantainer of >> the module. >> >> - [ ] The modules are considered "stable" by the majority of the PSC. >> >> - [x] The modules maintain 40% test coverage: (about 41% with Jacoco) >> >> - [x] The modules have no IP violations. >> >> - [x] The module has a page in the user manual: >> >> - [x] The maintainer (Mauro Bartolomeoli) has signed the GeoServer >> Contributor Agreement, also as a maintaner of other GeoServer features >> (WMTS cascading). >> >> >> >> If no objection arise, I would proceed creating a GSIP for this. >> >> >> >> -- >> >> Regards, >> >> Mauro Bartolomeoli >> >> == >> GeoServer Professional Services from the experts! Visit >> http://goo.gl/it488V for more information. >> == >> >> Dott. Mauro Bartolomeoli >> @mauro_bart >> Technical Lead >> >> GeoSolutions S.A.S. >> Via di Montramito 3/A >> 55054 Massarosa (LU) >> Italy >> >> mobile: +39 393 904 1756 >> phone: +39 0584 962313 >> fax: +39 0584 1660272 >> >> http://www.geo-solutions.it >> http://twitter.com/geosolutions_it >> >> --- >> >> >> >> *Con riferimento alla normativa sul trattamento dei dati personali (Reg. >> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si >> precisa che ogni circostanza inerente alla presente email (il suo >> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è >> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il >> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra >> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. >> This email is intended only for the person or entity to which it is >> addressed and may contain information that is privileged, confidential or >> otherwise protected from disclosure. We remind that - as provided by >> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this >> e-mail or the information herein by anyone other than the intended >> recipient is prohibited. If you have received this email by mistake, please >> notify us immediately by telephone or e-mail.* >> >> >> >> >> -- >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> ___ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> >> >> >> >> -- >> >> Regards, >> >> Mauro Bartolomeoli >> >> == >> GeoServer Professional Services from the experts! Visit >>
[Geoserver-devel] [JIRA] (GEOS-8897) Promote sldService community modules to extension (GSIP-170)
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-8897 Promote sldService community modules to extension (GSIP-170) Issue Type: Improvement Affects Versions: 2.14-beta Assignee: Mauro Bartolomeoli Components: sldservice Created: 20/Aug/18 3:45 PM Priority: Medium Reporter: Mauro Bartolomeoli GSIP at https://github.com/geoserver/geoserver/wiki/GSIP-170 Add Comment
Re: [Geoserver-devel] Promoting SLDservice community module to extension
GSIP is here: https://github.com/geoserver/geoserver/wiki/GSIP-170 Mauro Il giorno dom 29 lug 2018 alle ore 22:05 Andrea Aime < andrea.a...@geo-solutions.it> ha scritto: > Gsssipit! > > Cheers > Andrea > > Il Ven 27 Lug 2018, 19:21 Mauro Bartolomeoli < > mauro.bartolome...@geo-solutions.it> ha scritto: > >> Hi, I would like to propose SLDservice promotion to extension. >> >> Some of the requirements for promotion: >> >> - [x] The modules have at least a "handful" of users: recent interest in >> improvements to the module show that some people are using it. >> - [x] The modules have a designated and active maintainer: I contributed >> several improvements recently, and would like to become the mantainer of >> the module. >> - [ ] The modules are considered "stable" by the majority of the PSC. >> - [x] The modules maintain 40% test coverage: (about 41% with Jacoco) >> - [x] The modules have no IP violations. >> - [x] The module has a page in the user manual: >> - [x] The maintainer (Mauro Bartolomeoli) has signed the GeoServer >> Contributor Agreement, also as a maintaner of other GeoServer features >> (WMTS cascading). >> >> If no objection arise, I would proceed creating a GSIP for this. >> >> -- >> >> Regards, >> >> Mauro Bartolomeoli >> >> == >> GeoServer Professional Services from the experts! Visit >> http://goo.gl/it488V for more information. >> == >> >> Dott. Mauro Bartolomeoli >> @mauro_bart >> Technical Lead >> >> GeoSolutions S.A.S. >> Via di Montramito 3/A >> 55054 Massarosa (LU) >> Italy >> >> mobile: +39 393 904 1756 >> phone: +39 0584 962313 >> fax: +39 0584 1660272 >> >> http://www.geo-solutions.it >> http://twitter.com/geosolutions_it >> >> --- >> >> Con riferimento alla normativa sul trattamento dei dati personali (Reg. >> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si >> precisa che ogni circostanza inerente alla presente email (il suo >> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è >> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il >> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra >> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. >> >> This email is intended only for the person or entity to which it is >> addressed and may contain information that is privileged, confidential or >> otherwise protected from disclosure. We remind that - as provided by >> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this >> e-mail or the information herein by anyone other than the intended >> recipient is prohibited. If you have received this email by mistake, please >> notify us immediately by telephone or e-mail. >> >> >> -- >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> ___ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> > -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Promoting SLDservice community module to extension
Hi, I would like to propose SLDservice promotion to extension. Some of the requirements for promotion: - [x] The modules have at least a "handful" of users: recent interest in improvements to the module show that some people are using it. - [x] The modules have a designated and active maintainer: I contributed several improvements recently, and would like to become the mantainer of the module. - [ ] The modules are considered "stable" by the majority of the PSC. - [x] The modules maintain 40% test coverage: (about 41% with Jacoco) - [x] The modules have no IP violations. - [x] The module has a page in the user manual: - [x] The maintainer (Mauro Bartolomeoli) has signed the GeoServer Contributor Agreement, also as a maintaner of other GeoServer features (WMTS cascading). If no objection arise, I would proceed creating a GSIP for this. -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy mobile: +39 393 904 1756 phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-8841) SLD service: classify style for points doesn't include size, and this breaks WMS GetLegendGraphic
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-8841 SLD service: classify style for points doesn't include size, and this breaks WMS GetLegendGraphic Issue Type: Bug Affects Versions: 2.13.1 Assignee: Mauro Bartolomeoli Components: sldservice Created: 11/Jul/18 9:18 AM Priority: Medium Reporter: Mauro Bartolomeoli We should introduce a new optional parameter to set point size, and use a reasonable default if not specified Add Co
[Geoserver-devel] [JIRA] (GEOS-8836) SLD service: no stroke option not correctly handled for points
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-8836 SLD service: no stroke option not correctly handled for points Issue Type: Bug Assignee: Mauro Bartolomeoli Created: 10/Jul/18 12:07 PM Priority: Medium Reporter: Mauro Bartolomeoli Negative values for strokeWeight should be interpreted as "no stroke" 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#100088-sh
[Geoserver-devel] [JIRA] (GEOS-8832) SLDService: Add (optional and configurable) caching headers to the services responses
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-8832 SLDService: Add (optional and configurable) caching headers to the services responses Issue Type: Improvement Assignee: Mauro Bartolomeoli Created: 09/Jul/18 10:10 AM Priority: Medium Reporter: Mauro Bartolomeoli This would allow clients to cache classification results if needed 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#100088-sha1:89a39cb
[Geoserver-devel] [JIRA] (GEOS-8831) OneLogin community module tests are failing
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-8831 OneLogin community module tests are failing Issue Type: Bug Affects Versions: 2.14-beta Assignee: Mauro Bartolomeoli Components: onelogin Created: 09/Jul/18 9:59 AM Priority: Medium Reporter: Mauro Bartolomeoli Tests are failing due to a missing dependency to gs-security-tests Add Comment
Re: [Geoserver-devel] Optional caching of WMS GetMap remote style through SLD parameter
It should be doable. Version 4.x looks like a different beast (renamed to httpcomponents, a new package and probably some differences in the APIs), so they should not conflict. Mauro Il giorno ven 6 lug 2018 alle ore 10:00 Andrea Aime < andrea.a...@geo-solutions.it> ha scritto: > On Fri, Jul 6, 2018 at 9:52 AM, Mauro Bartolomeoli < > mauro.bartolome...@geo-solutions.it> wrote: > >> Hi, >> using the caching httpclient would require upgrading httpclient to >> version 4.1 (minimum). We currently use 3.1. Any concern with the eventual >> upgrade? >> > > Personally I would welcome the upgrade, even if just in that area, since > we have to eventually switch to it. > You just need to double check that the two versions of httpclient can live > toghether, if we don't have resources to do > a full switch (think geotools wms/wmts/wfs cascading, standalone gwc > commnication with wms services, wps > access to remote resources, and so on) > > Cheers > Andrea > > == > > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf > Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa > (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 > http://www.geo-solutions.it http://twitter.com/geosolutions_it > --- *Con riferimento > alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - > Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni > circostanza inerente alla presente email (il suo contenuto, gli eventuali > allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i > destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per > errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le > sarei comunque grato se potesse darmene notizia. This email is intended > only for the person or entity to which it is addressed and may contain > information that is privileged, confidential or otherwise protected from > disclosure. We remind that - as provided by European Regulation 2016/679 > “GDPR” - copying, dissemination or use of this e-mail or the information > herein by anyone other than the intended recipient is prohibited. If you > have received this email by mistake, please notify us immediately by > telephone or e-mail.* > -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Optional caching of WMS GetMap remote style through SLD parameter
Hi, using the caching httpclient would require upgrading httpclient to version 4.1 (minimum). We currently use 3.1. Any concern with the eventual upgrade? The alternative option of using guava-cache would not require any library update. Mauro Il giorno lun 2 lug 2018 alle ore 13:08 Andrea Aime < andrea.a...@geo-solutions.it> ha scritto: > Hi Mauro, > since some bits of HTTP caching headers support would be useful (if not > mandatory?) what about using > the one built into commons httpclient? (maybe via some customization) > https://hc.apache.org/httpcomponents-client-ga/tutorial/html/caching.html > > Cheers > Andrea > > On Mon, Jul 2, 2018 at 12:55 PM, Mauro Bartolomeoli < > mauro.bartolome...@geo-solutions.it> wrote: > >> Hi, >> I would like to introduce an optional cache for styles fetched by >> GeoServer through the WMS GetMap SLD parameter, to optimize the retrieval >> of dinamically generated SLD files that could require some time to be >> remotely generated. >> Any preference about the caching technology? >> I used guava caches in the past to implement authentication caches. Any >> concern in using a similar approach here? >> >> Many thanks. >> >> -- >> >> Regards, >> >> Mauro Bartolomeoli >> >> == >> GeoServer Professional Services from the experts! Visit >> http://goo.gl/it488V for more information. >> == >> >> Dott. Mauro Bartolomeoli >> @mauro_bart >> Technical Lead >> >> GeoSolutions S.A.S. >> Via di Montramito 3/A >> 55054 Massarosa (LU) >> Italy >> phone: +39 0584 962313 >> fax: +39 0584 1660272 >> >> http://www.geo-solutions.it >> http://twitter.com/geosolutions_it >> >> --- >> >> Con riferimento alla normativa sul trattamento dei dati personali (Reg. >> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si >> precisa che ogni circostanza inerente alla presente email (il suo >> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è >> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il >> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra >> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. >> >> This email is intended only for the person or entity to which it is >> addressed and may contain information that is privileged, confidential or >> otherwise protected from disclosure. We remind that - as provided by >> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this >> e-mail or the information herein by anyone other than the intended >> recipient is prohibited. If you have received this email by mistake, please >> notify us immediately by telephone or e-mail. >> >> >> >> -- >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> ___ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> >> > > > -- > > Regards, Andrea Aime == GeoServer Professional Services from the experts! > Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime > @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 > Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 > 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it > --- *Con riferimento > alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - > Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni > circostanza inerente alla presente email (il suo contenuto, gli eventuali > allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i > destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per > errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le > sarei comunque grato se potesse darmene notizia. This email is intended > only for the person or entity to which it is addressed and may contain > information that is privileged, confidential or otherwise protected from > disclosure. We remind that - as provided by European Regulation 2016/679 > “GDPR” - copying, dissemination or use of this e-mail or the information > herein by anyone other than the intended recipient is prohibited. If you > have received this email
[Geoserver-devel] [JIRA] (GEOS-8827) Introduce optional cache of remote styles in WMS
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-8827 Introduce optional cache of remote styles in WMS Issue Type: Improvement Affects Versions: 2.13.1 Assignee: Mauro Bartolomeoli Components: WMS Created: 06/Jul/18 9:39 AM Priority: Medium Reporter: Mauro Bartolomeoli We should introduce an optional and configurable cache for remote styles (those fetched through WMS GetMap SLD parameter) so that "slow" ones do not impact on performances. A
[Geoserver-devel] [JIRA] (GEOS-8823) SLD service improvements
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-8823 SLD service improvements Issue Type: Improvement Assignee: Mauro Bartolomeoli Components: sldservice Created: 05/Jul/18 4:34 PM Priority: Medium Reporter: Mauro Bartolomeoli SLDservice migration to the new REST infrastructure, inclusion in community builds and some improvements to the classify service: fullSLD mode custom classes custom list of colors (more than 3) Add Comment
Re: [Geoserver-devel] SLD service improvements
Hi Jody, I think the standard rest style endpoint requires using styles stored in GeoServer. SLDService, also for this use case, is about generating styles on the fly without storing them in GeoServer, so I think we cannot use the standard rest endpoint for this. Mauro Il giorno mer 4 lug 2018 alle ore 21:17 Jody Garnett ha scritto: > Should we not use the SLD standard GetStyle operation for this use case? > No need to make a new endpoint ... > > Even without supporting the other formats we should be able to generate an > SLD style for them (the existing rest endpoint can be used to convert > between style formats > <http://docs.geoserver.org/latest/en/user/styling/workshop/ysld/done.html#converting-to-ysld> > ). > -- > Jody Garnett > > > On Wed, 20 Jun 2018 at 02:48, Mauro Bartolomeoli < > mauro.bartolome...@geo-solutions.it> wrote: > >> Hi, >> I would like to introduce the possibility to return a full SLD from the >> sldservice / classify REST API (to be used, for example, in the SLD >> parameter of the WMS GetMap). >> >> Obviously, when returning the full SLD, other (non xml) formats would not >> be accepted. >> I can see two options: >> - adding a fullSLD (true/false) parameter to the actual classify REST >> controller; when true I would always return the full SLD ignoring the >> requested format (or eventually returning an exception if it's not XML) >> - adding a new specific entrypoint to the controller for the full SLD >> >> Any preference? >> >> I would also like to re-enable the build of the community module (I >> checked that now it compiles / work correctly with the new REST API >> library). >> >> -- >> >> Regards, >> >> Mauro Bartolomeoli >> >> == >> GeoServer Professional Services from the experts! Visit >> http://goo.gl/it488V for more information. >> == >> >> Dott. Mauro Bartolomeoli >> @mauro_bart >> Technical Lead >> >> GeoSolutions S.A.S. >> Via di Montramito 3/A >> 55054 Massarosa (LU) >> Italy >> phone: +39 0584 962313 >> fax: +39 0584 1660272 >> >> http://www.geo-solutions.it >> http://twitter.com/geosolutions_it >> >> --- >> >> Con riferimento alla normativa sul trattamento dei dati personali (Reg. >> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si >> precisa che ogni circostanza inerente alla presente email (il suo >> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è >> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il >> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra >> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. >> >> This email is intended only for the person or entity to which it is >> addressed and may contain information that is privileged, confidential or >> otherwise protected from disclosure. We remind that - as provided by >> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this >> e-mail or the information herein by anyone other than the intended >> recipient is prohibited. If you have received this email by mistake, please >> notify us immediately by telephone or e-mail. >> >> >> -- >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> ___ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> > -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se pote
Re: [Geoserver-devel] Optional caching of WMS GetMap remote style through SLD parameter
Hi Andrea, good idea, I will experiment a bit with that, thanks. Mauro Il giorno lun 2 lug 2018 alle ore 13:08 Andrea Aime < andrea.a...@geo-solutions.it> ha scritto: > Hi Mauro, > since some bits of HTTP caching headers support would be useful (if not > mandatory?) what about using > the one built into commons httpclient? (maybe via some customization) > https://hc.apache.org/httpcomponents-client-ga/tutorial/html/caching.html > > Cheers > Andrea > > On Mon, Jul 2, 2018 at 12:55 PM, Mauro Bartolomeoli < > mauro.bartolome...@geo-solutions.it> wrote: > >> Hi, >> I would like to introduce an optional cache for styles fetched by >> GeoServer through the WMS GetMap SLD parameter, to optimize the retrieval >> of dinamically generated SLD files that could require some time to be >> remotely generated. >> Any preference about the caching technology? >> I used guava caches in the past to implement authentication caches. Any >> concern in using a similar approach here? >> >> Many thanks. >> >> -- >> >> Regards, >> >> Mauro Bartolomeoli >> >> == >> GeoServer Professional Services from the experts! Visit >> http://goo.gl/it488V for more information. >> == >> >> Dott. Mauro Bartolomeoli >> @mauro_bart >> Technical Lead >> >> GeoSolutions S.A.S. >> Via di Montramito 3/A >> 55054 Massarosa (LU) >> Italy >> phone: +39 0584 962313 >> fax: +39 0584 1660272 >> >> http://www.geo-solutions.it >> http://twitter.com/geosolutions_it >> >> --- >> >> Con riferimento alla normativa sul trattamento dei dati personali (Reg. >> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si >> precisa che ogni circostanza inerente alla presente email (il suo >> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è >> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il >> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra >> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. >> >> This email is intended only for the person or entity to which it is >> addressed and may contain information that is privileged, confidential or >> otherwise protected from disclosure. We remind that - as provided by >> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this >> e-mail or the information herein by anyone other than the intended >> recipient is prohibited. If you have received this email by mistake, please >> notify us immediately by telephone or e-mail. >> >> >> >> -- >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> ___ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> >> > > > -- > > Regards, Andrea Aime == GeoServer Professional Services from the experts! > Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime > @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 > Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 > 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it > --- *Con riferimento > alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - > Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni > circostanza inerente alla presente email (il suo contenuto, gli eventuali > allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i > destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per > errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le > sarei comunque grato se potesse darmene notizia. This email is intended > only for the person or entity to which it is addressed and may contain > information that is privileged, confidential or otherwise protected from > disclosure. We remind that - as provided by European Regulation 2016/679 > “GDPR” - copying, dissemination or use of this e-mail or the information > herein by anyone other than the intended recipient is prohibited. If you > have received this email by mistake, please notify us immediately by > telephone or e-mail.* > -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Vis
[Geoserver-devel] Optional caching of WMS GetMap remote style through SLD parameter
Hi, I would like to introduce an optional cache for styles fetched by GeoServer through the WMS GetMap SLD parameter, to optimize the retrieval of dinamically generated SLD files that could require some time to be remotely generated. Any preference about the caching technology? I used guava caches in the past to implement authentication caches. Any concern in using a similar approach here? Many thanks. -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] SLD service improvements
Hi, an update on my work on SLDService, so that anyone interested can chime in with ideas: > > - adding a fullSLD (true/false) parameter to the actual classify REST > controller; when true I would always return the full SLD ignoring the > requested format (or eventually returning an exception if it's not XML) > First of all, I would go with adding the fullSLD parameter. In addition, to allow a more flexible usage of the service I would like to introduce a bunch of new paramters: - colors: list of comma delimited colors to generalize the current start, end and mid colors (to allow more precise palette specification from the client) - customClasses: list of comma delimited classes (each class is a semicolon delimited min, max and color list) to allow a completely client driven SLD generation (this is useful if the client allows the user to build a custom list of classes); the service would still be useful to translate the list to a real SLD (any preference for a distinct REST API entrypoint for this purpose?); obviously this makes sense if the # of classes is not that big - strokeWeight, strokeColor: a way to customize polygons stroke style instead of using the default one More important I will add support for viewparams, so that SQLViews can be used with the service too. -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] SLD service improvements
Hi, I would like to introduce the possibility to return a full SLD from the sldservice / classify REST API (to be used, for example, in the SLD parameter of the WMS GetMap). Obviously, when returning the full SLD, other (non xml) formats would not be accepted. I can see two options: - adding a fullSLD (true/false) parameter to the actual classify REST controller; when true I would always return the full SLD ignoring the requested format (or eventually returning an exception if it's not XML) - adding a new specific entrypoint to the controller for the full SLD Any preference? I would also like to re-enable the build of the community module (I checked that now it compiles / work correctly with the new REST API library). -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Upgrade printing-plugin to use geosolutions fork of mapfish-print 2.x
Hi, since probably upgrading our dependency on mapfish-print to latest versions is not going to happen quickly, I was wondering if switching to our improved 2.x version would be a good move. It would be a very low effort upgrade that will enable several improvements (one for all, clustering support). Other improvements are listed here: https://github.com/geosolutions-it/mapfish-print/wiki Any thought? -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-8627) WFS DataStore is missing some messages in translation files
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-8627 WFS DataStore is missing some messages in translation files Issue Type: Improvement Affects Versions: 2.13-RC1 Assignee: Mauro Bartolomeoli Components: Configuration Created: 08/Mar/18 5:09 PM Priority: Lowest Reporter: Mauro Bartolomeoli Some of the labels for WFS Cascading parameters UI are missing Add Comment
[Geoserver-devel] [JIRA] (GEOS-8537) jai-ext quantizer can sometimes exclude transparent colors from generated palette
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-8537 jai-ext quantizer can sometimes exclude transparent colors from generated palette Issue Type: Bug Affects Versions: 2.12.1 Assignee: Mauro Bartolomeoli Components: WMS Created: 18/Jan/18 10:20 AM Priority: Medium Reporter: Mauro Bartolomeoli Following up https://osgeo-org.atlassian.net/browse/GEOT-5925, we need to update jai-ext dependency to 1.0.19 Add Comment
[Geoserver-devel] Backporting GEOT-5903 and GEOS-8468
Hi, I would like to backport the work done to be able to override / extend the default LabelCache implementation in StreamingRenderer / WMS Ren deredImageMapOutputFormat. My targets for backporting are GS 2.12, 2.11 and 2.10 (GT 18.x, 17.x, and 16.x). Any blocker / concern? -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-8476) Allow parametric configuration of S3BlobStore
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-8476 Allow parametric configuration of S3BlobStore Issue Type: Improvement Affects Versions: 2.12.1 Assignee: Mauro Bartolomeoli Components: GWC-S3 Created: 07/Dec/17 12:01 PM Priority: Medium Reporter: Mauro Bartolomeoli Following up https://github.com/GeoWebCache/geowebcache/issues/568 https://github.com/GeoWebCache/geowebcache/pull/569 We need to enable this feature in gwc-s3 community module Add Comment
Re: [Geoserver-devel] Geoserver print module issue with WMS layers
Hi, this is usually a symptom of the request for getting the map image failing (it returns an XML instead of an image). You should have a look at GeoServer log files to understand if you can get the real exception. If you send me the log file of GeoServer immediately after a failing print I can try to help you. Mauro 2017-12-06 16:12 GMT+01:00 jcb81 : > Hello everyone, > > I searched for many hours for my issue, I hope I'll get some answers here. > > The context : I installed Geoserver (2.11.1) and configured some layers > coming from stores "Oracle NG" and "WMS". I also installed the print module > "Mapfish" to be able to send print request from a web application to > generate map reports. > > After many searches, I can now configure well the "config.yaml" file to > configure the print layouts, and I understand how works the GET and POST > http print requests and parameters. > > Here is my issue : the print request work well with layers coming from > "Oracle NG" store, but not the ones from the "WMS" store. When I download > the generated PDF, I get my report with a blank map and an exception > message > in a little yellow box near the map area : "java.io.IOException: The byte > array is not a recognized imageformat." > > <http://osgeo-org.1560.x6.nabble.com/file/t370398/ > mapfish_print_error_1.png> > <http://osgeo-org.1560.x6.nabble.com/file/t370398/ > mapfish_print_error_2.png> > > Here is a working request : > http://localhost:9100/geoserver/pdf/print.pdf?spec={ > outputFilename:'print-${MMddHHmmss}',layout:'MY_ > MAP_LAYOUT',pages:[{center:[88861.938477485,100786.976035025],scale:1, > rotation:0}],dpi:75,units:'m',srs:'EPSG:2169',layers:[{baseURL:' > http://localhost:9100/geoserver/wms',type:'WMS' > ,layers:['WS:ORACLE_LAYER'],format:'image/png'}]} > > Here is a NOT working request : > http://localhost:9100/geoserver/pdf/print.pdf?spec={ > outputFilename:'print-${MMddHHmmss}',layout:'MY_ > MAP_LAYOUT',pages:[{center:[88861.938477485,100786.976035025],scale:1, > rotation:0}],dpi:75,units:'m',srs:'EPSG:2169',layers:[{baseURL:' > http://localhost:9100/geoserver/wms',type:'WMS',layers:['WS:WMS_LAYER'], > format:'image/png'}]} > > Only the layer asked changes in the parameters. > > The only thing I found for now is about authentification issue on WMS > layers, but my WMS layers don't have any authentification, they can be > reached as it. > > Is anyone here already had this issue ? Or have an explanation on what I'm > doing wrong ? > Any help will be really appreciated ! > > > > -- > Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-Dev-f3819232.html > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any
[Geoserver-devel] [JIRA] (GEOS-8468) Allow setting an alternative LabelCache implementation in RenderedImageMapOutputFormat
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-8468 Allow setting an alternative LabelCache implementation in RenderedImageMapOutputFormat Issue Type: Improvement Affects Versions: 2.12.1 Assignee: Mauro Bartolomeoli Components: WMS Created: 04/Dec/17 6:24 PM Priority: Medium Reporter: Mauro Bartolomeoli Allowing overriding the LabelCache implementation is already implemented in StreamingRenderer, though the LABEL_CACHE_KEY rendering hint. We should introduce an optional property in RenderedImageMapOutputFormat, so that we can override the implementation for WMS image output format(s). Add Comment
[Geoserver-devel] Backporting
Hi, I would like to backport the following to 2.11: GEOS-8267: added support for viewParams in WPS Execute embedded WFS requests any concern? -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Some changes to LabelCache / RenderImageMapOutputFormat to ease customization
Hi, I would like to refactor LabelCacheImpl a bit to allow extending / overriding it and introduce custom behaviour through extension. What I would do: - remove final from the class definition - transform some method from private to protected to allow overriding Then, I would like to add a setLabelCache method in RenderImageMapOutputFormat, so that I can override the default LabelCache implementation with my own. Any concern with this? If anyone is curious, I am builiding a LabelCache implementation that is able to mask labels using a footprint. -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Issue with DataStore wrappers in NewLayerPage
GeoServer PR is ready: https://github.com/geoserver/geoserver/pull/2669 Mauro 2017-11-27 12:50 GMT+01:00 Andrea Aime : > On Wed, Nov 22, 2017 at 12:21 PM, Mauro Bartolomeoli < > mauro.bartolome...@geo-solutions.it> wrote: > >> Hi, >> my only concern in using the sql interface is that both methods in it >> throw SQLException(s). Should we extend it to throw a more >> geotools-friendly exception? >> > > I agree having a SQLException in that class seems out of place > > Cheers > Andrea > > > -- > > Regards, > > Andrea Aime > > == > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions S.A.S. > Via di Montramito 3/A > <https://maps.google.com/?q=Via+di+Montramito+3/A+55054+%C2%A0Massarosa&entry=gmail&source=g> > 55054 Massarosa > <https://maps.google.com/?q=Via+di+Montramito+3/A+55054+%C2%A0Massarosa&entry=gmail&source=g> > (LU) > phone: +39 0584 962313 <+39%200584%20962313> > fax: +39 0584 1660272 <+39%200584%20166%200272> > mob: +39 339 8844549 <+39%20339%20884%204549> > > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > > AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 > > Le informazioni contenute in questo messaggio di posta elettronica e/o > nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il > loro utilizzo è consentito esclusivamente al destinatario del messaggio, > per le finalità indicate nel messaggio stesso. Qualora riceviate questo > messaggio senza esserne il destinatario, Vi preghiamo cortesemente di > darcene notizia via e-mail e di procedere alla distruzione del messaggio > stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, > divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od > utilizzarlo per finalità diverse, costituisce comportamento contrario ai > principi dettati dal D.Lgs. 196/2003. > > The information in this message and/or attachments, is intended solely for > the attention and use of the named addressee(s) and may be confidential or > proprietary in nature or covered by the provisions of privacy act > (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection > Code).Any use not in accord with its purpose, any disclosure, reproduction, > copying, distribution, or either dissemination, either whole or partial, is > strictly forbidden except previous formal approval of the named > addressee(s). If you are not the intended recipient, please contact > immediately the sender by telephone, fax or e-mail and delete the > information in this message that has been received in error. The sender > does not give any warranty or accept liability as the content, accuracy or > completeness of sent messages and accepts no responsibility for changes > made after they were sent or for other risks which arise as a result of > e-mail transmission, viruses, etc. > > -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone,
Re: [Geoserver-devel] Issue with DataStore wrappers in NewLayerPage
Started porting the "wrappers" to GeoTools: https://github.com/geotools/geotools/pull/1752 Anyone wishing to review? Mauro 2017-11-22 12:21 GMT+01:00 Mauro Bartolomeoli < mauro.bartolome...@geo-solutions.it>: > Hi, > my only concern in using the sql interface is that both methods in it > throw SQLException(s). Should we extend it to throw a more > geotools-friendly exception? > > 2017-11-22 10:18 GMT+01:00 Andrea Aime : > >> On Wed, Nov 22, 2017 at 9:55 AM, Mauro Bartolomeoli < >> mauro.bartolome...@geo-solutions.it> wrote: >> >>> I created a couple of issues for GT / GS related to this: >>> >>> https://osgeo-org.atlassian.net/browse/GEOT-5883 >>> https://osgeo-org.atlassian.net/browse/GEOS-8411 >>> >>> Is a proposal required for this? >>> >> >> Hum... if we end up using a Java interface for unwrapping and also >> considering the classes involved >> have been private business of the security subsystem so far, I personally >> do not see the need for >> a proposal. But that's just me :-) >> >> Cheers >> Andrea >> >> -- >> >> Regards, >> >> Andrea Aime >> >> == >> GeoServer Professional Services from the experts! Visit >> http://goo.gl/it488V for more information. >> == >> >> Ing. Andrea Aime >> @geowolf >> Technical Lead >> >> GeoSolutions S.A.S. >> Via di Montramito 3/A >> <https://maps.google.com/?q=Via+di+Montramito+3/A+55054+%C2%A0Massarosa&entry=gmail&source=g> >> 55054 Massarosa >> <https://maps.google.com/?q=Via+di+Montramito+3/A+55054+%C2%A0Massarosa&entry=gmail&source=g> >> (LU) >> phone: +39 0584 962313 <+39%200584%20962313> >> fax: +39 0584 1660272 <+39%200584%20166%200272> >> mob: +39 339 8844549 <+39%20339%20884%204549> >> >> http://www.geo-solutions.it >> http://twitter.com/geosolutions_it >> >> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 >> >> Le informazioni contenute in questo messaggio di posta elettronica e/o >> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il >> loro utilizzo è consentito esclusivamente al destinatario del messaggio, >> per le finalità indicate nel messaggio stesso. Qualora riceviate questo >> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di >> darcene notizia via e-mail e di procedere alla distruzione del messaggio >> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, >> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od >> utilizzarlo per finalità diverse, costituisce comportamento contrario ai >> principi dettati dal D.Lgs. 196/2003. >> >> The information in this message and/or attachments, is intended solely >> for the attention and use of the named addressee(s) and may be confidential >> or proprietary in nature or covered by the provisions of privacy act >> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection >> Code).Any use not in accord with its purpose, any disclosure, reproduction, >> copying, distribution, or either dissemination, either whole or partial, is >> strictly forbidden except previous formal approval of the named >> addressee(s). If you are not the intended recipient, please contact >> immediately the sender by telephone, fax or e-mail and delete the >> information in this message that has been received in error. The sender >> does not give any warranty or accept liability as the content, accuracy or >> completeness of sent messages and accepts no responsibility for changes >> made after they were sent or for other risks which arise as a result of >> e-mail transmission, viruses, etc. >> >> > > > -- > > Regards, > > Mauro Bartolomeoli > > == > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. > == > > Dott. Mauro Bartolomeoli > @mauro_bart > Technical Lead > > GeoSolutions S.A.S. > Via di Montramito 3/A > 55054 Massarosa (LU) > Italy > phone: +39 0584 962313 <+39%200584%20962313> > fax: +39 0584 1660272 <+39%200584%20166%200272> > > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > > --- > > AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 > > Le informazioni contenute in questo messaggio di posta elettronica e/o > nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il > loro utilizzo è consentito esclusivamente al destinat
Re: [Geoserver-devel] Issue with DataStore wrappers in NewLayerPage
Hi, my only concern in using the sql interface is that both methods in it throw SQLException(s). Should we extend it to throw a more geotools-friendly exception? 2017-11-22 10:18 GMT+01:00 Andrea Aime : > On Wed, Nov 22, 2017 at 9:55 AM, Mauro Bartolomeoli < > mauro.bartolome...@geo-solutions.it> wrote: > >> I created a couple of issues for GT / GS related to this: >> >> https://osgeo-org.atlassian.net/browse/GEOT-5883 >> https://osgeo-org.atlassian.net/browse/GEOS-8411 >> >> Is a proposal required for this? >> > > Hum... if we end up using a Java interface for unwrapping and also > considering the classes involved > have been private business of the security subsystem so far, I personally > do not see the need for > a proposal. But that's just me :-) > > Cheers > Andrea > > -- > > Regards, > > Andrea Aime > > == > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions S.A.S. > Via di Montramito 3/A > <https://maps.google.com/?q=Via+di+Montramito+3/A+55054+%C2%A0Massarosa&entry=gmail&source=g> > 55054 Massarosa > <https://maps.google.com/?q=Via+di+Montramito+3/A+55054+%C2%A0Massarosa&entry=gmail&source=g> > (LU) > phone: +39 0584 962313 <+39%200584%20962313> > fax: +39 0584 1660272 <+39%200584%20166%200272> > mob: +39 339 8844549 <+39%20339%20884%204549> > > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > > AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 > > Le informazioni contenute in questo messaggio di posta elettronica e/o > nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il > loro utilizzo è consentito esclusivamente al destinatario del messaggio, > per le finalità indicate nel messaggio stesso. Qualora riceviate questo > messaggio senza esserne il destinatario, Vi preghiamo cortesemente di > darcene notizia via e-mail e di procedere alla distruzione del messaggio > stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, > divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od > utilizzarlo per finalità diverse, costituisce comportamento contrario ai > principi dettati dal D.Lgs. 196/2003. > > The information in this message and/or attachments, is intended solely for > the attention and use of the named addressee(s) and may be confidential or > proprietary in nature or covered by the provisions of privacy act > (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection > Code).Any use not in accord with its purpose, any disclosure, reproduction, > copying, distribution, or either dissemination, either whole or partial, is > strictly forbidden except previous formal approval of the named > addressee(s). If you are not the intended recipient, please contact > immediately the sender by telephone, fax or e-mail and delete the > information in this message that has been received in error. The sender > does not give any warranty or accept liability as the content, accuracy or > completeness of sent messages and accepts no responsibility for changes > made after they were sent or for other risks which arise as a result of > e-mail transmission, viruses, etc. > > -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code)
Re: [Geoserver-devel] Issue with DataStore wrappers in NewLayerPage
I created a couple of issues for GT / GS related to this: https://osgeo-org.atlassian.net/browse/GEOT-5883 https://osgeo-org.atlassian.net/browse/GEOS-8411 Is a proposal required for this? Mauro 2017-11-20 17:07 GMT+01:00 Mauro Bartolomeoli < mauro.bartolome...@geo-solutions.it>: > Hi, > DecoratingStore is already implementing this: > > https://github.com/geoserver/geoserver/blob/master/src/ > main/src/main/java/org/geoserver/catalog/Wrapper.java > > From a first look, it seems a copy of the jdbc one :-) > > We can probably use this interface in NewLayerPage to unwrap the > DataStore. I would anyway port all the chain (from Wrapper to > DecoratingDatastore) in Geotools. > What do you think? > > Mauro > > 2017-11-20 10:44 GMT+01:00 Jody Garnett : > >> It may be worth introducing something more generic like >> https://docs.oracle.com/javase/7/docs/api/java/sql/Wrapper.html >> On Mon, Nov 20, 2017 at 8:22 PM Mauro Bartolomeoli < >> mauro.bartolome...@geo-solutions.it> wrote: >> >>> Hi, >>> there is an issue in the NewLayerPage UI, where a couple of options are >>> nade visible for specific datastores. >>> In particular there is a bug preventing the "Configure cascaded stored >>> query..." for WFSDataStore to appear. >>> This happens because the option visibility is based on a >>> instanceof WFSDataStore condition, that does not match because the >>> datastore is wrapped by a RetypingDataStore. >>> >>> Long story short, we should allow unwrapping those kind of datastores in >>> a generic way, in my opinion. >>> >>> My idea would be to introduce a WrappingDataStore interface with a >>> single getWrapped method that would be implemented by RetypingDataStore >>> (and others). >>> Any opinion on this? >>> >>> >>> -- >>> >>> Regards, >>> >>> Mauro Bartolomeoli >>> >>> == >>> GeoServer Professional Services from the experts! Visit >>> http://goo.gl/it488V for more information. >>> == >>> >>> Dott. Mauro Bartolomeoli >>> @mauro_bart >>> Technical Lead >>> >>> GeoSolutions S.A.S. >>> Via di Montramito 3/A >>> <https://maps.google.com/?q=Via+di+Montramito+3/A+55054+%C2%A0Massarosa&entry=gmail&source=g> >>> 55054 Massarosa >>> <https://maps.google.com/?q=Via+di+Montramito+3/A+55054+%C2%A0Massarosa&entry=gmail&source=g> >>> (LU) >>> Italy >>> phone: +39 0584 962313 <+39%200584%20962313> >>> fax: +39 0584 1660272 <+39%200584%20166%200272> >>> >>> http://www.geo-solutions.it >>> http://twitter.com/geosolutions_it >>> >>> --- >>> >>> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 >>> >>> Le informazioni contenute in questo messaggio di posta elettronica e/o >>> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il >>> loro utilizzo è consentito esclusivamente al destinatario del messaggio, >>> per le finalità indicate nel messaggio stesso. Qualora riceviate questo >>> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di >>> darcene notizia via e-mail e di procedere alla distruzione del messaggio >>> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, >>> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od >>> utilizzarlo per finalità diverse, costituisce comportamento contrario ai >>> principi dettati dal D.Lgs. 196/2003. >>> >>> The information in this message and/or attachments, is intended solely >>> for the attention and use of the named addressee(s) and may be confidential >>> or proprietary in nature or covered by the provisions of privacy act >>> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection >>> Code).Any use not in accord with its purpose, any disclosure, reproduction, >>> copying, distribution, or either dissemination, either whole or partial, is >>> strictly forbidden except previous formal approval of the named >>> addressee(s). If you are not the intended recipient, please contact >>> immediately the sender by telephone, fax or e-mail and delete the >>> information in this message that has been received in error. The sender >>> does not give any warranty or accept liability as the content, accuracy or >>> completeness of sent messages and accepts no responsibi
[Geoserver-devel] [JIRA] (GEOS-8411) Wrapped DataStore prevents the "Configure cascaded stored query..." for WFSDataStore to appear.
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-8411 Wrapped DataStore prevents the "Configure cascaded stored query..." for WFSDataStore to appear. Issue Type: Bug Affects Versions: 2.12.1 Assignee: Mauro Bartolomeoli Components: web Created: 22/Nov/17 9:54 AM Priority: Medium Reporter: Mauro Bartolomeoli Currently the instanceof WFSDataStore check fails because the store is wrapped in a RetypingDataStore. This would be helped by solving this first : https://osgeo-org.atlassian.net/browse/GEOT-5883 A
Re: [Geoserver-devel] Issue with DataStore wrappers in NewLayerPage
Hi, DecoratingStore is already implementing this: https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/geoserver/catalog/Wrapper.java >From a first look, it seems a copy of the jdbc one :-) We can probably use this interface in NewLayerPage to unwrap the DataStore. I would anyway port all the chain (from Wrapper to DecoratingDatastore) in Geotools. What do you think? Mauro 2017-11-20 10:44 GMT+01:00 Jody Garnett : > It may be worth introducing something more generic like > https://docs.oracle.com/javase/7/docs/api/java/sql/Wrapper.html > On Mon, Nov 20, 2017 at 8:22 PM Mauro Bartolomeoli < > mauro.bartolome...@geo-solutions.it> wrote: > >> Hi, >> there is an issue in the NewLayerPage UI, where a couple of options are >> nade visible for specific datastores. >> In particular there is a bug preventing the "Configure cascaded stored >> query..." for WFSDataStore to appear. >> This happens because the option visibility is based on a >> instanceof WFSDataStore condition, that does not match because the >> datastore is wrapped by a RetypingDataStore. >> >> Long story short, we should allow unwrapping those kind of datastores in >> a generic way, in my opinion. >> >> My idea would be to introduce a WrappingDataStore interface with a single >> getWrapped method that would be implemented by RetypingDataStore (and >> others). >> Any opinion on this? >> >> >> -- >> >> Regards, >> >> Mauro Bartolomeoli >> >> == >> GeoServer Professional Services from the experts! Visit >> http://goo.gl/it488V for more information. >> == >> >> Dott. Mauro Bartolomeoli >> @mauro_bart >> Technical Lead >> >> GeoSolutions S.A.S. >> Via di Montramito 3/A >> <https://maps.google.com/?q=Via+di+Montramito+3/A+55054+%C2%A0Massarosa&entry=gmail&source=g> >> 55054 Massarosa >> <https://maps.google.com/?q=Via+di+Montramito+3/A+55054+%C2%A0Massarosa&entry=gmail&source=g> >> (LU) >> Italy >> phone: +39 0584 962313 <+39%200584%20962313> >> fax: +39 0584 1660272 <+39%200584%20166%200272> >> >> http://www.geo-solutions.it >> http://twitter.com/geosolutions_it >> >> --- >> >> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 >> >> Le informazioni contenute in questo messaggio di posta elettronica e/o >> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il >> loro utilizzo è consentito esclusivamente al destinatario del messaggio, >> per le finalità indicate nel messaggio stesso. Qualora riceviate questo >> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di >> darcene notizia via e-mail e di procedere alla distruzione del messaggio >> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, >> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od >> utilizzarlo per finalità diverse, costituisce comportamento contrario ai >> principi dettati dal D.Lgs. 196/2003. >> >> The information in this message and/or attachments, is intended solely >> for the attention and use of the named addressee(s) and may be confidential >> or proprietary in nature or covered by the provisions of privacy act >> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection >> Code).Any use not in accord with its purpose, any disclosure, reproduction, >> copying, distribution, or either dissemination, either whole or partial, is >> strictly forbidden except previous formal approval of the named >> addressee(s). If you are not the intended recipient, please contact >> immediately the sender by telephone, fax or e-mail and delete the >> information in this message that has been received in error. The sender >> does not give any warranty or accept liability as the content, accuracy or >> completeness of sent messages and accepts no responsibility for changes >> made after they were sent or for other risks which arise as a result of >> e-mail transmission, viruses, etc. >> >> ---- >> -- >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot__ >> _ >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> > -- > -- > Jody Garnett > -- Regards, Mau
[Geoserver-devel] Issue with DataStore wrappers in NewLayerPage
Hi, there is an issue in the NewLayerPage UI, where a couple of options are nade visible for specific datastores. In particular there is a bug preventing the "Configure cascaded stored query..." for WFSDataStore to appear. This happens because the option visibility is based on a instanceof WFSDataStore condition, that does not match because the datastore is wrapped by a RetypingDataStore. Long story short, we should allow unwrapping those kind of datastores in a generic way, in my opinion. My idea would be to introduce a WrappingDataStore interface with a single getWrapped method that would be implemented by RetypingDataStore (and others). Any opinion on this? -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-8269) SUBPROCESS xml is malformed in WPS Request Builder
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-8269 SUBPROCESS xml is malformed in WPS Request Builder Issue Type: Improvement Affects Versions: 2.11.2 Assignee: Unassigned Components: WPS Created: 05/Sep/17 10:35 AM Priority: Medium Reporter: Mauro Bartolomeoli When defining a subprocess for the features input in the WPS request builder, the related XML is wrongly encoded (no content for Identifier, DataInputs, ResponseForm tags) Example: http://schemas.opengis.net/wps/1.0.0/wpsAll.xsd"> Add
Re: [Geoserver-devel] beta release / code freeze warning
Hi, is the freeze active, or I can merge this PR: https://github.com/geoserver/geoserver/pull/2504 ? Thanks 2017-08-22 20:30 GMT+02:00 Jody Garnett : > Welcome back from foss4g, we have a GeoServer 2.12-beta release scheduled > for this week, > > I would like to start the geoserver release process on Sundary (this is a > weekend activity) - please reply to this thread if you have any > functionality or fix trying to sneak in under the wire. > > The beta release marks the start of our code freeze, during the code > freeze we will not be accepting new functionality onto master - allowing > the team to focus on bug fixes. > -- > Jody Garnett > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > > -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Adding support for viewParams in WPS embedded WFS requests
Hi, I opened a JIRA issue (https://osgeo-org.atlassian.net/browse/GEOS-8267) and created a pull request for this: https://github.com/geoserver/geoserver/pull/2504 Please, kindly review. Mauro 2017-08-29 14:18 GMT+02:00 Andrea Aime : > On Tue, Aug 29, 2017 at 2:04 PM, Mauro Bartolomeoli < > mauro.bartolome...@geo-solutions.it> wrote: > >> Can you think of a simpler / cleaner approach? >> >> Maybe we can create a GS WFSDelegate that is using full GS >> WFSConfiguration objects, instead of the GT ones. >> > > Hi Mauro, > I believe this one looks good. Using the WFS one would be interesting too, > the only downside I see is > that it would bind WPS startup to the presence of WFS in the classpath... > which in theory is a problem, > WPS should be able to work without WFS around, but in fact I don't know if > that's already the case > (I would guess WPS cannot start already without WFS around) and WFS is a > core module anyways. > > Just creating a class at runtime should not prevent startup, should only > cause failure in when the > object is actually instantiated. > > So... unsure, maybe leave it like you did it. > > Cheers > Andrea > > -- > > Regards, > > Andrea Aime > > == > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions S.A.S. > Via di Montramito 3/A > 55054 Massarosa (LU) > phone: +39 0584 962313 <+39%200584%20962313> > fax: +39 0584 1660272 <+39%200584%20166%200272> > mob: +39 339 8844549 <+39%20339%20884%204549> > > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > > AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 > > Le informazioni contenute in questo messaggio di posta elettronica e/o > nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il > loro utilizzo è consentito esclusivamente al destinatario del messaggio, > per le finalità indicate nel messaggio stesso. Qualora riceviate questo > messaggio senza esserne il destinatario, Vi preghiamo cortesemente di > darcene notizia via e-mail e di procedere alla distruzione del messaggio > stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, > divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od > utilizzarlo per finalità diverse, costituisce comportamento contrario ai > principi dettati dal D.Lgs. 196/2003. > > The information in this message and/or attachments, is intended solely for > the attention and use of the named addressee(s) and may be confidential or > proprietary in nature or covered by the provisions of privacy act > (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection > Code).Any use not in accord with its purpose, any disclosure, reproduction, > copying, distribution, or either dissemination, either whole or partial, is > strictly forbidden except previous formal approval of the named > addressee(s). If you are not the intended recipient, please contact > immediately the sender by telephone, fax or e-mail and delete the > information in this message that has been received in error. The sender > does not give any warranty or accept liability as the content, accuracy or > completeness of sent messages and accepts no responsibility for changes > made after they were sent or for other risks which arise as a result of > e-mail transmission, viruses, etc. > > -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be c
[Geoserver-devel] [JIRA] (GEOS-8267) Enable usage of viewParams in WPS embedded WFS requests
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-8267 Enable usage of viewParams in WPS embedded WFS requests Issue Type: Improvement Affects Versions: 2.11.2 Assignee: Mauro Bartolomeoli Components: WPS Created: 30/Aug/17 9:28 AM Priority: Medium Reporter: Mauro Bartolomeoli The current parser for WFS GetFeature requests embedded in WPS Execute requests does not recognize GeoServer vendor params, such as viewParams. Having support for viewparams will enable full usage of SQLView driven featuretype in WPS processes. Add Comment
[Geoserver-devel] Adding support for viewParams in WPS embedded WFS requests
Hi, currently you cannot specify the viewParams attribute in a WFS GetFeature request embedded in a WPS Execute statement. This is because parsing of WFS requests is done through geotools bindings that are not aware of the viewParams attribute. Having viewParams support is a nice improvement, in my opinion, since it opens new scenarios for WPS processes involving sqlviews driven feature types. I tried an approach to get this done, and it's working, but I would like to get more opinions on the "cleanest" way to do this kind of things. Basically, what I tried to do is to replace the XSDDelegate responsible for WFS requests parsing used in GeoTools with a custom one, using GeoServer GetFeatureTypeBinding implementation (that is able to parse GeoServer vendor params). This is the related snippet in GS WPSConfiguration: protected void configureContext(MutablePicoContainer container) { super.configureContext(container); ... Object wfsDelegate = container.getComponentInstanceOfType(WFSParserDelegate.class); container.unregisterComponentByInstance(wfsDelegate); container.registerComponentInstance(new XSDParserDelegate(new WFSConfiguration() { @Override protected void configureBindings(MutablePicoContainer container) { super.configureBindings(container); container.registerComponentImplementation(WFS.GetFeatureType, GetFeatureTypeBinding.class); } })); } Can you think of a simpler / cleaner approach? Maybe we can create a GS WFSDelegate that is using full GS WFSConfiguration objects, instead of the GT ones. Any other idea? -- Regards, Mauro Bartolomeoli == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Backporting GEOS-8022
Hi, I would like to ask permission for backporting GEOS-8022: disabling usage of dynamic styles for WMS requests (globally or on specific virtual services). It should be considered a small improvement, in my opinion. I would backport to 2.11 and 2.10. Any opinion? Regards, Mauro Bartolomeoli -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Senior Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Disabling SLD and SLD_BODY in WMS requests
Hi, I prepared a PR for this: https://github.com/geoserver/geoserver/pull/2144 Please, review if you wish. Regards, Mauro 2017-03-02 9:54 GMT+01:00 Andrea Aime : > On Thu, Mar 2, 2017 at 9:48 AM, Ian Turton wrote: > >> I agree it sounds like a good idea, is there some way to signal in the >> capabilities document that these functions are or are not available? >> > > Err... we should first advertise that they are there, we don't .. :-p > > Cheers > Andrea > > > -- > == > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions S.A.S. > Via di Montramito 3/A > 55054 Massarosa (LU) > phone: +39 0584 962313 <+39%200584%20962313> > fax: +39 0584 1660272 <+39%200584%20166%200272> > mob: +39 339 8844549 <+39%20339%20884%204549> > > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > > *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* > > Le informazioni contenute in questo messaggio di posta elettronica e/o > nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il > loro utilizzo è consentito esclusivamente al destinatario del messaggio, > per le finalità indicate nel messaggio stesso. Qualora riceviate questo > messaggio senza esserne il destinatario, Vi preghiamo cortesemente di > darcene notizia via e-mail e di procedere alla distruzione del messaggio > stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, > divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od > utilizzarlo per finalità diverse, costituisce comportamento contrario ai > principi dettati dal D.Lgs. 196/2003. > > > > The information in this message and/or attachments, is intended solely for > the attention and use of the named addressee(s) and may be confidential or > proprietary in nature or covered by the provisions of privacy act > (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection > Code).Any use not in accord with its purpose, any disclosure, reproduction, > copying, distribution, or either dissemination, either whole or partial, is > strictly forbidden except previous formal approval of the named > addressee(s). If you are not the intended recipient, please contact > immediately the sender by telephone, fax or e-mail and delete the > information in this message that has been received in error. The sender > does not give any warranty or accept liability as the content, accuracy or > completeness of sent messages and accepts no responsibility for changes > made after they were sent or for other risks which arise as a result of > e-mail transmission, viruses, etc. > > --- > -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Senior Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after t
[Geoserver-devel] [JIRA] (GEOS-8022) Allow disabling usage of SLD and SLD_BODY in WMS requests (also for virtual services)
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-8022 Allow disabling usage of SLD and SLD_BODY in WMS requests (also for virtual services) Issue Type: Improvement Affects Versions: 2.11-beta Assignee: Mauro Bartolomeoli Components: WMS Created: 07/Mar/17 10:00 AM Priority: Medium Reporter: Mauro Bartolomeoli Currently this is possible with the GeoFence extension. We should move this functionality to core and remove it from GeoFence Add Comment
[Geoserver-devel] Disabling SLD and SLD_BODY in WMS requests
Hi, we would like to move a functionality currently available in GeoFence to GeoServer core. This is the ability to disable the usage of SLD and SLD_BODY in WMS requests, globally or on a workspace by workspace basis. The plan is to: - add a new option in WMS config page to disable SLD and SLD_BODY - change WMS requests flow to take care of the option and launch an exception when needed - remove the analogous flag from GeoFence Any opinion / doubt? Regards, Mauro -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Senior Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Server restart required to register LDAP roles
Hi Torben, I looked a little bit more into the issue you reported. It seems to work as expected to me. Going to explain: you can give admin rights to users coming from LDAP in two ways: 1) using the LDAP Authentication Provider only, and filling the groups section as explained here: http://docs.geoserver.org/latest/en/user/security/tutorials/ldap/index.html#map-ldap-groups-to-geoserver-roles; a role service is not needed for this. After doing that, bill can log in with admin rights (I was able to do that on a fresh 2.10.1 installation). Question: did you login with bill credentials before mapping the groups (then you could experience caching issues)? 2) creating an LDAP role service as explained here: http://docs.geoserver.org/latest/en/user/security/tutorials/ldap/index.html#configure-the-ldap-role-service and setting that role service as the active one (this is not mentioned in the tutorial, where the role service is created, but not really enabled for active usage); the purpose of the tutorial was to enable seeing roles from LDAP in the authorizations sections (data / services), not enabling the role service for role binding; we can probably add a sentence or two in the tutorial to clarify this Regards, Mauro Bartolomeoli 2017-01-19 1:56 GMT+01:00 Torben Barsballe : > I was testing out the GeoServer Authentication > <http://docs.geoserver.org/latest/en/user/security/tutorials/ldap/index.html>with > LDAP tutorial, and ran into this issue. > > After Step 5 of Map LDAP groups to GeoServer roles > <http://docs.geoserver.org/latest/en/user/security/tutorials/ldap/index.html#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. > > Reported as https://osgeo-org.atlassian.net/browse/GEOS-7936 > > > I am not quite sure if this a documentation error with the tutorial, or a > regression in the LDAP security settings. If anyone with more experience > using the LDAP provider knows which of these is more likely, your knowledge > would be appreciated. > > Note that I was able to reproduce this issue with GeoServer 2.8.3 as well. > > > Torben > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > > -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Server restart required to register LDAP roles
Hi Torben, > I am not quite sure if this a documentation error with the tutorial, or a > regression in the LDAP security settings. If anyone with more experience > using the LDAP provider knows which of these is more likely, your knowledge > would be appreciated. > It looks more like a regression. For sure it is not the intended behaviour. Regards, Mauro Bartolomeoli -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Senior Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-7834) WMS GetLegendGraphic margins issues
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-7834 WMS GetLegendGraphic margins issues Issue Type: Improvement Affects Versions: 2.10.0 Assignee: Mauro Bartolomeoli Created: 03/Nov/16 4:51 PM Priority: Medium Reporter: Mauro Bartolomeoli I would like to propose a couple of new options for the GetLegendGraphic WMS request: labelMargin, to set the margin between icons and the related labels; I would use a default of 2/3 pixels so that labels have a small distance from the icons; currently for icons that are filling the given space (usually external images) there is no space between the icon and the label absoluteMargins (true|false): this is for raster legends; currently a proportional margin is applied, so that space between columns depends (for example) from labels text length; when absoluteMargins is true, I would use a fixed space margin (configurable with the already existing dx option); I would also switch to absolute margins by default (I don't really understand the usage of proportional space between co
[Geoserver-devel] WMS GetLegendGraphic
Hi, I would like to propose a couple of new options for the GetLegendGraphic WMS request: - labelMargin, to set the margin between icons and the related labels; I would use a default of 2/3 pixels so that labels have a small distance from the icons; currently for icons that are filling the given space (usually external images) there is no space between the icon and the label An example with the (default) 3 pixels: [image: Immagine incorporata 3] An example with a 10 pixels margin: [image: Immagine incorporata 4] - absoluteMargins (true|false): this is for raster legends; currently a proportional margin is applied, so that space between columns depends (for example) from labels text length; when absoluteMargins is true, I would use a fixed space margin (configurable with the already existing dx option); I would also switch to absolute margins by default (I don't really understand the usage of proportional space between columns) An example with proportional margins: [image: Immagine incorporata 2] With absolute margins I would get: [image: Immagine incorporata 1] Any thoughts? Regards, Mauro -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Senior Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. -- The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Old JIRA for CAS extension
Hi, 2016-10-20 12:36 GMT+02:00 Christian Mueller < christian.muel...@os-solutions.at>: > Please merge :-) > > Done. > A backport would be nice. > 2.10, 2.9, 2.8 is ok? Mauro -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Senior Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Old JIRA for CAS extension
Hi Christian and all, I prepared the related (trivial) pull request here: https://github.com/geoserver/geoserver/pull/1899 Mauro 2016-10-20 9:20 GMT+02:00 Christian Mueller < christian.muel...@os-solutions.at>: > Hi Mauro > > I tested the first patch in my online test environment --> no issues, > seems to be correct. > > The second patch is not up to date, the code does not contain a call > > getHandler().recordSession(httpReq); > > I think we should apply the first patch. > > Christian > > > On Wed, Oct 19, 2016 at 12:22 PM, Mauro Bartolomeoli < > mauro.bartolome...@geo-solutions.it> wrote: > >> Hi everybody, >> I was asked by one of our customers to investigate if >> https://osgeo-org.atlassian.net/browse/GEOS-6189 is still current and if >> we can apply the patch that's attached to the JIRA ticket. >> >> Basically, they are experiencing some issues with single sign out. >> >> I will try to explain what I have understood so far about the proposed >> patches. >> >> *First patch:* >> >> In GeoServerCasAuthenticationFilter there is some code to handle single >> sign out: >> >>if (isLogoutRequest(httpReq)) { >> if (singleSignOut) { // do we participate >> LOGGER.info("Single Sign Out received from CAS server --> >> starting log out"); >> handler.process(httpReq, httpRes); >> LogoutFilterChain logOutChain = (LogoutFilterChain) >> >> getSecurityManager().getSecuri >> tyConfig().getFilterChain().getRequestChainByName("webLogout"); >> logOutChain.doLogout(getSecurityManager(), httpReq, >> httpRes,getName()); >> >> } else >> LOGGER.info("Single Sign Out received from CAS server --> >> ignoring"); >> return; >> } >> >> The handler.process(...) call is handling the CAS related logout, but it >> seems that doing that before calling the GeoServer logout chaing is the >> cause of issues, so we suggest to move the code this way: >> >>if (isLogoutRequest(httpReq)) { >> if (singleSignOut) { // do we participate >> LOGGER.info("Single Sign Out received from CAS server --> >> starting log out"); >> LogoutFilterChain logOutChain = (LogoutFilterChain) >> getSecurityManager().getSecuri >> tyConfig().getFilterChain().getRequestChainByName("webLogout"); >> logOutChain.doLogout(getSecurityManager(), httpReq, >> httpRes,getName()); >> handler.process(httpReq, httpRes); >> } else >> LOGGER.info("Single Sign Out received from CAS server --> >> ignoring"); >> return; >> } >> >> This makes sense to me and I did some tests to see if it breaks the >> logout scenario, with no issues. >> >> *Second patch:* >> >> Another piece of code is registering the CAS token when available so that >> it can be used during the single logut procedure. >> >> if (SecurityContextHolder.getContext().getAuthentication()!=null) { >> HttpSession session = httpReq.getSession(false); >> >> if (session !=null && >> session.getAttribute(GeoServer >> CasConstants.CAS_ASSERTION_KEY)!=null && singleSignOut) { >> handler.process(httpReq, httpRes); >> >> if (LOGGER.isLoggable(Level.INFO)) >> LOGGER.info("Record HTTP Session "+session.getId()+ " >> for CAS single sign out"); >> } >> } >> >> The patch proposes to remove this piece of code, but in my opinion this >> is not correct, since then the single sign out procedure would not be able >> to find the token when needed. >> >> My idea would be to apply only the first patch, and I will prepare a pull >> request for that. Is there any CAS expert out there that can give me >> advices on this? >> >> Thanks >> Mauro >> >> -- >> == >> GeoServer Professional Services from the experts! Visit >> http://goo.gl/it488V for more information. >> == >> >> Dott. Mauro Bartolomeoli >> @mauro_bart >> Senior Software Engineer >> >> GeoSolutions S.A.S. >> Via di Montramito 3/A >> 55054 Massarosa (LU) >> Italy >> phone: +39 0584 962313
[Geoserver-devel] Old JIRA for CAS extension
Hi everybody, I was asked by one of our customers to investigate if https://osgeo-org.atlassian.net/browse/GEOS-6189 is still current and if we can apply the patch that's attached to the JIRA ticket. Basically, they are experiencing some issues with single sign out. I will try to explain what I have understood so far about the proposed patches. *First patch:* In GeoServerCasAuthenticationFilter there is some code to handle single sign out: if (isLogoutRequest(httpReq)) { if (singleSignOut) { // do we participate LOGGER.info("Single Sign Out received from CAS server --> starting log out"); handler.process(httpReq, httpRes); LogoutFilterChain logOutChain = (LogoutFilterChain) getSecurityManager().getSecurityConfig().getFilterChain().getRequestChainByName("webLogout"); logOutChain.doLogout(getSecurityManager(), httpReq, httpRes,getName()); } else LOGGER.info("Single Sign Out received from CAS server --> ignoring"); return; } The handler.process(...) call is handling the CAS related logout, but it seems that doing that before calling the GeoServer logout chaing is the cause of issues, so we suggest to move the code this way: if (isLogoutRequest(httpReq)) { if (singleSignOut) { // do we participate LOGGER.info("Single Sign Out received from CAS server --> starting log out"); LogoutFilterChain logOutChain = (LogoutFilterChain) getSecurityManager().getSecurityConfig().getFilterChain().getRequestChainByName("webLogout"); logOutChain.doLogout(getSecurityManager(), httpReq, httpRes,getName()); handler.process(httpReq, httpRes); } else LOGGER.info("Single Sign Out received from CAS server --> ignoring"); return; } This makes sense to me and I did some tests to see if it breaks the logout scenario, with no issues. *Second patch:* Another piece of code is registering the CAS token when available so that it can be used during the single logut procedure. if (SecurityContextHolder.getContext().getAuthentication()!=null) { HttpSession session = httpReq.getSession(false); if (session !=null && session.getAttribute(GeoServerCasConstants.CAS_ASSERTION_KEY)!=null && singleSignOut) { handler.process(httpReq, httpRes); if (LOGGER.isLoggable(Level.INFO)) LOGGER.info("Record HTTP Session "+session.getId()+ " for CAS single sign out"); } } The patch proposes to remove this piece of code, but in my opinion this is not correct, since then the single sign out procedure would not be able to find the token when needed. My idea would be to apply only the first patch, and I will prepare a pull request for that. Is there any CAS expert out there that can give me advices on this? Thanks Mauro -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Dott. Mauro Bartolomeoli @mauro_bart Senior Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or
Re: [Geoserver-devel] New Community Module: OneLogin Authentication
Hi everybody, the freeze is finished and I updated the pull request for the OneLogin community module so that it builds with 2.11-SNAPSHOT. If no one has objections I would merge it tomorrow. Any objections? Regards, Mauro 2016-09-27 14:20 GMT+02:00 Mauro Bartolomeoli < mauro.bartolome...@geo-solutions.it>: > Hi, I prepared a pull request for this: https://github.com/ > geoserver/geoserver/pull/1851 > > Thanks > Mauro > > > 2016-09-26 9:57 GMT+02:00 Mauro Bartolomeoli solutions.it>: > >> HI Christian, the work is based on spring-security-saml2-core, which is >> in turn base on opensaml. >> >> Mauro >> >> 2016-09-24 5:40 GMT+02:00 Christian Mueller < >> christian.muel...@os-solutions.at>: >> >>> +1 >>> >>> Will you use https://wiki.shibboleth.net/confluence/display/OS30/Home ? >>> >>> Cheers >>> Christian >>> >>> On Fri, Sep 23, 2016 at 10:04 PM, Ben Caradoc-Davies >>> wrote: >>> >>>> +1. That sounds quite useful. >>>> >>>> Kind regards, >>>> Ben. >>>> >>>> On 24/09/16 03:03, Mauro Bartolomeoli wrote: >>>> > Dear All, >>>> > I am asking for the permission to create a new community module for >>>> > GeoServer to allow it to authenticate users against the OneLogin SSO >>>> > service (https://www.onelogin.com/). >>>> > >>>> > OneLogin uses the SAML protocol for its SSO implementation, so this >>>> work >>>> > could be used as a base for a more generic SAML provider in the >>>> future. >>>> > >>>> > Please, vote. >>>> > >>>> > Thanks >>>> > Mauro >>>> > >>>> > >>>> > >>>> > >>>> > >>>> -- >>>> > >>>> > >>>> > >>>> > ___ >>>> > Geoserver-devel mailing list >>>> > Geoserver-devel@lists.sourceforge.net >>>> > https://lists.sourceforge.net/lists/listinfo/geoserver-devel >>>> > >>>> >>>> -- >>>> Ben Caradoc-Davies >>>> Director >>>> Transient Software Limited <http://transient.nz/> >>>> New Zealand >>>> >>>> >>>> -- >>>> ___ >>>> Geoserver-devel mailing list >>>> Geoserver-devel@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >>>> >>> >>> >>> >>> -- >>> DI Christian Mueller MSc (GIS), MSc (IT-Security) >>> OSS Open Source Solutions GmbH >>> >>> >> >> >> -- >> == >> GeoServer Professional Services from the experts! Visit >> http://goo.gl/it488V for more information. >> == >> >> Dott. Mauro Bartolomeoli >> @mauro_bart >> Senior Software Engineer >> >> GeoSolutions S.A.S. >> Via di Montramito 3/A >> 55054 Massarosa (LU) >> Italy >> phone: +39 0584 962313 >> fax: +39 0584 1660272 >> >> http://www.geo-solutions.it >> http://twitter.com/geosolutions_it >> >> --- >> >> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* >> >> Le informazioni contenute in questo messaggio di posta elettronica e/o >> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il >> loro utilizzo è consentito esclusivamente al destinatario del messaggio, >> per le finalità indicate nel messaggio stesso. Qualora riceviate questo >> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di >> darcene notizia via e-mail e di procedere alla distruzione del messaggio >> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, >> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od >> utilizzarlo per finalità diverse, costituisce comportamento contrario ai >> principi dettati dal D.Lgs. 196/2003. >> >> >> >> The information in this message and/or attachments, is intended solely >> for the attention and use of the named addressee(s) and may be confidential >> or proprietary in nature or covered by the provisions of p
Re: [Geoserver-devel] New Community Module: OneLogin Authentication
Hi, I prepared a pull request for this: https://github.com/geoserver/geoserver/pull/1851 Thanks Mauro 2016-09-26 9:57 GMT+02:00 Mauro Bartolomeoli < mauro.bartolome...@geo-solutions.it>: > HI Christian, the work is based on spring-security-saml2-core, which is in > turn base on opensaml. > > Mauro > > 2016-09-24 5:40 GMT+02:00 Christian Mueller solutions.at>: > >> +1 >> >> Will you use https://wiki.shibboleth.net/confluence/display/OS30/Home ? >> >> Cheers >> Christian >> >> On Fri, Sep 23, 2016 at 10:04 PM, Ben Caradoc-Davies >> wrote: >> >>> +1. That sounds quite useful. >>> >>> Kind regards, >>> Ben. >>> >>> On 24/09/16 03:03, Mauro Bartolomeoli wrote: >>> > Dear All, >>> > I am asking for the permission to create a new community module for >>> > GeoServer to allow it to authenticate users against the OneLogin SSO >>> > service (https://www.onelogin.com/). >>> > >>> > OneLogin uses the SAML protocol for its SSO implementation, so this >>> work >>> > could be used as a base for a more generic SAML provider in the future. >>> > >>> > Please, vote. >>> > >>> > Thanks >>> > Mauro >>> > >>> > >>> > >>> > >>> > >>> -- >>> > >>> > >>> > >>> > ___ >>> > Geoserver-devel mailing list >>> > Geoserver-devel@lists.sourceforge.net >>> > https://lists.sourceforge.net/lists/listinfo/geoserver-devel >>> > >>> >>> -- >>> Ben Caradoc-Davies >>> Director >>> Transient Software Limited <http://transient.nz/> >>> New Zealand >>> >>> >>> -- >>> ___ >>> Geoserver-devel mailing list >>> Geoserver-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >>> >> >> >> >> -- >> DI Christian Mueller MSc (GIS), MSc (IT-Security) >> OSS Open Source Solutions GmbH >> >> > > > -- > == > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. > == > > Dott. Mauro Bartolomeoli > @mauro_bart > Senior Software Engineer > > GeoSolutions S.A.S. > Via di Montramito 3/A > 55054 Massarosa (LU) > Italy > phone: +39 0584 962313 > fax: +39 0584 1660272 > > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > > --- > > *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* > > Le informazioni contenute in questo messaggio di posta elettronica e/o > nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il > loro utilizzo è consentito esclusivamente al destinatario del messaggio, > per le finalità indicate nel messaggio stesso. Qualora riceviate questo > messaggio senza esserne il destinatario, Vi preghiamo cortesemente di > darcene notizia via e-mail e di procedere alla distruzione del messaggio > stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, > divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od > utilizzarlo per finalità diverse, costituisce comportamento contrario ai > principi dettati dal D.Lgs. 196/2003. > > > > The information in this message and/or attachments, is intended solely for > the attention and use of the named addressee(s) and may be confidential or > proprietary in nature or covered by the provisions of privacy act > (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection > Code).Any use not in accord with its purpose, any disclosure, reproduction, > copying, distribution, or either dissemination, either whole or partial, is > strictly forbidden except previous formal approval of the named > addressee(s). If you are not the intended recipient, please contact > immediately the sender by telephone, fax or e-mail and delete the > information in this message that has been received in error. The sender > does not give any warranty or accept liability as the content, accuracy or > completeness of sent messages and accepts no responsibility for changes > made after they were sent or for other risks which arise as a result of > e-mail transmission, viruses, etc. > -- == GeoServer Prof
[Geoserver-devel] [JIRA] (GEOS-7770) Communtiy Module: OneLogin Authentication Filter
Title: Message Title Mauro Bartolomeoli created an issue GeoServer / GEOS-7770 Communtiy Module: OneLogin Authentication Filter Issue Type: Improvement Affects Versions: 2.10-beta Assignee: Mauro Bartolomeoli Components: Community modules, Security Created: 27/Sep/16 12:16 PM Priority: Medium Reporter: Mauro Bartolomeoli We should add a new community module implementing SingleSignOn through OneLogin services Add Comment