[Geoserver-devel] Build failed in Jenkins: GeoServer-2.8.x » XLST based WFS output format #208

2016-03-15 Thread winbuild 
See 


--
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
[INFO] 
[INFO] 
[INFO] Building XLST based WFS output format 2.8-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ gs-xslt ---
[INFO] Deleting 
C:\.jenkins\jobs\GeoServer-2.8.x\workspace\src\extension\xslt\target
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:clean (default) @ gs-xslt ---
[INFO] 
[INFO] --- git-commit-id-plugin:2.0.4:revision (default) @ gs-xslt ---
[INFO] [GitCommitIdMojo] Running on 
'c:\.jenkins\jobs\GeoServer-2.8.x\workspace\.git' repository...
[INFO] [GitCommitIdMojo] Initializing properties...
[INFO] [GitCommitIdMojo] Using maven project properties...
[INFO] [GitCommitIdMojo] Loading data from git repository...
[INFO] [GitCommitIdMojo] --git properties 
loaded--
[INFO] [GitCommitIdMojo] build.commit.message.short = Merge pull request #1532 
from ridethepenguin/secureddatastoreinfo-bug-2.8.x
[INFO] [GitCommitIdMojo] build.build.user.email = Unknown
[INFO] [GitCommitIdMojo] build.hudsonId = -1
[INFO] [GitCommitIdMojo] build.commit.time = 15.03.2016 @ 20:34:05 CET
[INFO] [GitCommitIdMojo] build.timestamp = 15-mar-2016 21:09
[INFO] [GitCommitIdMojo] build.build.time = 15.03.2016 @ 21:58:38 CET
[INFO] [GitCommitIdMojo] build.branch = 8dae366ad0836e4b6f425c2b86a2603971b0930d
[INFO] [GitCommitIdMojo] build.commit.user.email = b...@transient.nz
[INFO] [GitCommitIdMojo] build.build.user.name = Unknown
[INFO] [GitCommitIdMojo] build.commit.user.name = Ben Caradoc-Davies
[INFO] [GitCommitIdMojo] build.commit.id.abbrev = 8dae366
[INFO] [GitCommitIdMojo] build.commit.id = 
8dae366ad0836e4b6f425c2b86a2603971b0930d
[INFO] [GitCommitIdMojo] build.commit.message.full = Merge pull request #1532 
from ridethepenguin/secureddatastoreinfo-bug-2.8.x

[GEOS-7459] Securing an app-schema data store may result in ClassCastException 
being thrown
[INFO] [GitCommitIdMojo] 
-
[INFO] [GitCommitIdMojo] Finished running.
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ gs-xslt 
---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 5 resources
[INFO] skip non existing resourceDirectory 
C:\.jenkins\jobs\GeoServer-2.8.x\workspace\src\extension\xslt\src\main\resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ gs-xslt ---
[INFO] Compiling 12 source files to 
C:\.jenkins\jobs\GeoServer-2.8.x\workspace\src\extension\xslt\target\classes
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
gs-xslt ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO] Copying 8 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
gs-xslt ---
[INFO] Compiling 4 source files to 
C:\.jenkins\jobs\GeoServer-2.8.x\workspace\src\extension\xslt\target\test-classes
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.3:test (default-test) @ gs-xslt ---
[INFO] Surefire report directory: 
C:\.jenkins\jobs\GeoServer-2.8.x\workspace\src\extension\xslt\target\surefire-reports

---
 T E S T S
---
Running org.geoserver.wfs.xslt.GetFeatureXSLTTest
Formats are: {HTML=HTML, text/html; subtype=xslt=text/html; subtype=xslt}
Tests run: 10, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 17.706 sec <<< 
FAILURE!
testNoOutputFormats(org.geoserver.wfs.xslt.GetFeatureXSLTTest)  Time elapsed: 
94 sec  <<< ERROR!
java.lang.IllegalStateException: Cannot create wfs/transform
at 
org.geoserver.platform.resource.FileSystemResourceStore$FileSystemResource.dir(FileSystemResourceStore.java:340)
at 
org.geoserver.config.GeoServerDataDirectory.findOrCreateDir(GeoServerDataDirectory.java:139)
at 
org.geoserver.wfs.xslt.config.TransformRepository.getAllTransforms(TransformRepository.java:173)
at 
org.geoserver.wfs.xslt.XSLTOutputFormatUpdater.run(XSLTOutputFormatUpdater.java:43)
at 
org.geoserver.wfs.xslt.GetFeatureXSLTTest.testNoOutputFormats(GetFeatureXSLTTest.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at

[Geoserver-devel] Build failed in Jenkins: GeoServer-2.8.x #208

2016-03-15 Thread winbuild 
See 

Changes:

[ridethepenguin] [GEOS-7459] Securing an app-schema data store may result in 
ClassCastException being thrown

--
[...truncated 14750 lines...]
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at 
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at 
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
Caused by: java.io.FileNotFoundException: Unable to create 
C:\.jenkins\jobs\GeoServer-2.8.x\workspace\src\extension\xslt\.\target\default7809591383106635364data\wfs\transform
at 
org.geoserver.platform.resource.FileSystemResourceStore$FileSystemResource.dir(FileSystemResourceStore.java:332)
... 38 more

Running org.geoserver.wfs.xslt.config.TransformRepositoryTest
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.418 sec
Running org.geoserver.wfs.xslt.rest.TransformRestTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.761 sec

Results :

Tests in error: 
  testNoOutputFormats(org.geoserver.wfs.xslt.GetFeatureXSLTTest): Cannot create 
wfs/transform

Tests run: 29, Failures: 0, Errors: 1, Skipped: 0

[JENKINS] Recording test results
[JENKINS] Archiving disabled
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] GeoServer . SUCCESS [15.741s]
[INFO] Core Platform Module .. SUCCESS [21.231s]
[INFO] Open Web Service Module ... SUCCESS [19.484s]
[INFO] Main Module ... SUCCESS [4:09.680s]
[INFO] GeoServer Security Modules  SUCCESS [0.609s]
[INFO] GeoServer JDBC Security Module  SUCCESS [33.218s]
[INFO] GeoServer LDAP Security Module  SUCCESS [14.165s]
[INFO] Web Coverage Service Module ... SUCCESS [4.259s]
[INFO] Web Coverage Service 1.0 Module ... SUCCESS [1:08.921s]
[INFO] Web Coverage Service 1.1 Module ... SUCCESS [1:14.287s]
[INFO] Web Coverage Service 2.0 Module ... SUCCESS [2:06.735s]
[INFO] Web Feature Service Module  SUCCESS [3:20.990s]
[INFO] Web Map Service Module  SUCCESS [5:08.880s]
[INFO] KML support for GeoServer . SUCCESS [55.397s]
[INFO] GeoWebCache (GWC) Module .. SUCCESS [2:08.570s]
[INFO] REST Support Module ... SUCCESS [25.693s]
[INFO] REST Configuration Service Module . SUCCESS [3:24.781s]
[INFO] GeoServer Web Modules . SUCCESS [0.265s]
[INFO] Core UI Module  SUCCESS [2:00.932s]
[INFO] WMS UI Module . SUCCESS [37.441s]
[INFO] GWC UI Module . SUCCESS [1:13.620s]
[INFO] WFS UI Module . SUCCESS [18.533s]
[INFO] Demoes Module . SUCCESS [36.800s]
[INFO] WCS UI Module . SUCCESS [25.802s]
[INFO] Security UI Modules ... SUCCESS [0.639s]
[INFO] Security UI Core Module ... SUCCESS [2:21.477s]
[INFO] Security UI JDBC Module ... SUCCESS [1:35.322s]
[INFO] Security UI LDAP Module ... SUCCESS [25.725s]
[INFO] REST UI Module  SUCCESS [20.592s]
[INFO] GeoServer Web Application . SUCCESS [15.367s]
[INFO] Community Space ... SUCCESS [0.296s]
[INFO]

Re: [Geoserver-devel] Travis builds not helping pull requests anymore

2016-03-15 Thread Andrea Aime 
On Tue, Mar 15, 2016 at 7:58 PM, Andrea Aime 
wrote:

> This one keeps on being a mystery, done a dependency:tree on the 1.1.13
>> release and there are no snapshots in the tree:
>>
>
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @
> imageio-ext-turbojpeg ---
> [INFO] it.geosolutions.imageio-ext:imageio-ext-turbojpeg:jar:1.1.13
> [INFO] +-
> it.geosolutions.imageio-ext:imageio-ext-streams:jar:1.1.13:compile
> [INFO] +-
> it.geosolutions.imageio-ext:imageio-ext-imagereadmt:jar:1.1.13:compile
> [INFO] +- it.geosolutions.imageio-ext:imageio-ext-test-data:jar:1.1.13:test
> [INFO] +-
> it.geosolutions.imageio-ext:imageio-ext-utilities:jar:1.1.13:compile
> [INFO] +- org.libjpegturbo:turbojpeg-wrapper:jar:1.2.1.1:compile
> [INFO] +- commons-io:commons-io:jar:1.4:compile
> [INFO] +- junit:junit:jar:4.11:test
> [INFO] |  \- org.hamcrest:hamcrest-core:jar:1.3:test
> [INFO] +- javax.media:jai_core:jar:1.1.3:compile
> [INFO] +- javax.media:jai_codec:jar:1.1.3:compile
> [INFO] \- javax.media:jai_imageio:jar:1.1:compile
>
>
Ah, found it, in the boundless repo we have in the turbojpeg-wrapper pom:

http://maven.apache.org/POM/4.0.0; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;>
4.0.0

it.geosolutions.imageio-ext
imageio-ext-library
   * 1.2-SNAPSHOT*


org.libjpegturbo
turbojpeg-wrapper
1.2.1.1
jar
Libjpegturbo java wrapper



However in the tag the parent is correct, looks like a deploy issue:

https://github.com/geosolutions-it/imageio-ext/blob/1.1.13/library/libjpegturbo/pom.xml

Wondering, will a manual redeploy on the geosolutions repository also fix
the boundless
one?

Cheers
Andrea

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

Ing. Andrea Aime
@geowolf
Technical Lead

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

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.



The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

---
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Travis builds not helping pull requests anymore

2016-03-15 Thread Andrea Aime 
On Mon, Mar 14, 2016 at 9:28 PM, Andrea Aime 
wrote:

> Hi,
> most of the pull request builds are failing due to errors like the
> following:
>
> [ERROR] Failed to execute goal on project gs-libjpeg-turbo: Could not resolve 
> dependencies for project 
> org.geoserver.extension:gs-libjpeg-turbo:jar:2.9-SNAPSHOT: Failed to collect 
> dependencies at it.geosolutions.imageio-ext:imageio-ext-turbojpeg:jar:1.1.13 
> -> org.libjpegturbo:turbojpeg-wrapper:jar:1.2.1.1: Failed to read artifact 
> descriptor for org.libjpegturbo:turbojpeg-wrapper:jar:1.2.1.1: Could not find 
> artifact it.geosolutions.imageio-ext:imageio-ext-library:pom:1.2-SNAPSHOT in 
> boundless (https://repo.boundlessgeo.com/main/) -> [Help 1]
> [ERROR] Failed to execute goal on project gs-monitor-core: Could not resolve 
> dependencies for project 
> org.geoserver.extension:gs-monitor-core:jar:2.9-SNAPSHOT: Could not find 
> artifact com.maxmind:geoip:jar:1.2.3 in boundless 
> (https://repo.boundlessgeo.com/main/) -> [Help 1]
> [ERROR] Failed to execute goal on project gs-importer-bdb: Could not resolve 
> dependencies for project 
> org.geoserver.importer:gs-importer-bdb:jar:2.9-SNAPSHOT: Could not find 
> artifact com.sleepycat:je:jar:4.1.10 in boundless 
> (https://repo.boundlessgeo.com/main/) -> [Help 1]
>
> I'm a bit weirded out by the first ending up looking for a SNAPSHOT, the
> jpeg-turbo pom does not have SNAPSHOT dependencies,
> but I'll have a better look tomorrow.
>

This one keeps on being a mystery, done a dependency:tree on the 1.1.13
release and there are no snapshots in the tree:

[INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @
imageio-ext-turbojpeg ---
[INFO] it.geosolutions.imageio-ext:imageio-ext-turbojpeg:jar:1.1.13
[INFO] +- it.geosolutions.imageio-ext:imageio-ext-streams:jar:1.1.13:compile
[INFO] +-
it.geosolutions.imageio-ext:imageio-ext-imagereadmt:jar:1.1.13:compile
[INFO] +- it.geosolutions.imageio-ext:imageio-ext-test-data:jar:1.1.13:test
[INFO] +-
it.geosolutions.imageio-ext:imageio-ext-utilities:jar:1.1.13:compile
[INFO] +- org.libjpegturbo:turbojpeg-wrapper:jar:1.2.1.1:compile
[INFO] +- commons-io:commons-io:jar:1.4:compile
[INFO] +- junit:junit:jar:4.11:test
[INFO] |  \- org.hamcrest:hamcrest-core:jar:1.3:test
[INFO] +- javax.media:jai_core:jar:1.1.3:compile
[INFO] +- javax.media:jai_codec:jar:1.1.3:compile
[INFO] \- javax.media:jai_imageio:jar:1.1:compile



> The other two are clearer, we depend on some old jars that are no more
> available in central and that are now
> not available on the boundless repo either (they were available on the old
> repo.opengeo.org though).
>
> Is that stuff that can added back by a manual install?
>

I've manually deployed them in the release repository, let's see if that's
enough to get Travis back in business...

Cheers
Andrea

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

Ing. Andrea Aime
@geowolf
Technical Lead

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

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.



The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

---

[Geoserver-devel] [JIRA] (GEOS-7462) Threads updating the GWC disk quota can get blocked indefinitely on configuration reload

2016-03-15 Thread Andrea Aime [Administrator] (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrea Aime [Administrator] created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-7462  
 
 
  Threads updating the GWC disk quota can get blocked indefinitely on configuration reload   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 15/Mar/16 5:16 PM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Andrea Aime [Administrator]  
 

  
 
 
 
 

 
 This can happen if a configuration reload happens while threads are trying to put quota size update diffs on an already full diff queue: 
 
The threads get blocked on the full queue 
The reload triggers a restart of the disk quota subsystem, with the creation of a new queue 
The old queue never gets cleaned and the old threads never get freed (there is no timeout on the queue offering) 
 Eventually the server will run out of threads that can be used to serve requests (to get the effect quicker, install control-flow to limit the number of requests that can actually run).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Re: [Geoserver-devel] Standardize URL of WMS endpoint in GetCapabilities response

2016-03-15 Thread Andrea Aime 
On Tue, Mar 15, 2016 at 3:46 PM, Damiano Albani 
wrote:

> Yes, it would be nice to have that discussion about the service endpoints.
> Although the current behavior provides a lot a flexibility (simply by
> adding the appropriate "=XYZ"), it makes things messy and not very
> logical in my opinion.
>
> A concrete example of where this is an issue, is when trying to limit
> access to specific protocols, when GeoServer is running behind a reverse
> proxy.
>

Ah, now this is a problem, because we cannot stop responding to the old
paths either, it would be a severe backwards compatibility issue.


> But as you said that the "correct" endpoint URL is "/ows?SERVICE=XYZ&",
> that means that such a reverse proxy would have to check the query
> parameters anyway.
>

Right. Securing OGC protocols by reverse proxy is going to be a lot of pain
anyways, think also about the POST requests
that are accepted in most protocols (yes, also in WMS).
A few year ago we looked into it and decided that going the "security
proxy" was going to be too much of a pain, and
developed a different approach instead:
http://demo.geo-solutions.it/share/securing_geoserver.pdf

I'd suggest you have a look at the ResourceAccessManager interface, the
default security subsystem implementation
possibly to GeoFence as examples of implementation of that concept.

Cheers
Andrea


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

Ing. Andrea Aime
@geowolf
Technical Lead

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

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.



The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

---
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Standardize URL of WMS endpoint in GetCapabilities response

2016-03-15 Thread Damiano Albani 
On Tue, Mar 15, 2016 at 3:29 PM, Andrea Aime 
wrote:

> By the way, the usage of "ows" in the caps documents has been ignored for
> so much time that I guess it could
> be put on the discussion table again. I have no strong opinion on the
> matter, to GeoServer wms/wcs/wps/ows
> are all the same (you can literally use geoserver/workspace/wms to make a
> wfs request if you want to,
> unless you're forgetting to add =WFS in the URL it should not make
> any difference).
> E.g.:
>
>
> http://demo.geo-solutions.it/geoserver/tiger/wms?service=WFS=1.0.0=GetFeature=tiger:tiger_roads=50
>
> And oh, noticed that the preview is indeed using "ows" for WFS, but "wms"
> for WMS preview links... LOL :-)
>

Yes, it would be nice to have that discussion about the service endpoints.
Although the current behavior provides a lot a flexibility (simply by
adding the appropriate "=XYZ"), it makes things messy and not very
logical in my opinion.

A concrete example of where this is an issue, is when trying to limit
access to specific protocols, when GeoServer is running behind a reverse
proxy.
But as you said that the "correct" endpoint URL is "/ows?SERVICE=XYZ&",
that means that such a reverse proxy would have to check the query
parameters anyway.

-- 
*Damiano Albani*
Geodan
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Standardize URL of WMS endpoint in GetCapabilities response

2016-03-15 Thread Andrea Aime 
On Tue, Mar 15, 2016 at 3:32 PM, Damiano Albani 
wrote:

> On Tue, Mar 15, 2016 at 3:19 PM, Andrea Aime  > wrote:
>
>>
>> Only because they were developed by different people in different times.
>> That said, the "right" version is almost the WMS one,
>> it should be using "ows", the service named endpoints wms/wfs/wps and so
>> on are kept, as far as I know, for backwards compatibility only. It should
>> be "http://host/geoserver/workspace/ows;.
>>
>
> So should it open a JIRA for this enhancement, expecting "ows" as the
> desired base endpoint for all protocols?
>

If you plan to implement it, I guess so, yes.
Here is our current take on improvement/feature requests:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer

This probably needs a bit of discussion/agreement before being implemented,
but should be fine.


>
> Speaking of minor differences between protocols, I've also seen that
> GetCapabilities for WCS *requires* an uppercase service name.
> Calling "ows?request=GetCapabilities=*wcs*" will fail:
>
>> Error in service name, epected value: WCS
>> []
>
>
>
That is correct and standard compliant, the OGC specification demands key
values to be treated as case sensitive (only the keys itself
are case insensitive, e.g., SeRvICe=WCS is correct, service=wcs is not).
In various other protocols we have extra leniency and also accept lowercase
values, but that's also for backwards compatibility

Cheers
Andrea


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

Ing. Andrea Aime
@geowolf
Technical Lead

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

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.



The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

---
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Standardize URL of WMS endpoint in GetCapabilities response

2016-03-15 Thread Damiano Albani 
On Tue, Mar 15, 2016 at 3:19 PM, Andrea Aime 
wrote:

>
> Only because they were developed by different people in different times.
> That said, the "right" version is almost the WMS one,
> it should be using "ows", the service named endpoints wms/wfs/wps and so
> on are kept, as far as I know, for backwards compatibility only. It should
> be "http://host/geoserver/workspace/ows;.
>

So should it open a JIRA for this enhancement, expecting "ows" as the
desired base endpoint for all protocols?

Speaking of minor differences between protocols, I've also seen that
GetCapabilities for WCS *requires* an uppercase service name.
Calling "ows?request=GetCapabilities=*wcs*" will fail:

> Error in service name, epected value: WCS
> []


-- 
*Damiano Albani*
Geodan
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Standardize URL of WMS endpoint in GetCapabilities response

2016-03-15 Thread Andrea Aime 
By the way, the usage of "ows" in the caps documents has been ignored for
so much time that I guess it could
be put on the discussion table again. I have no strong opinion on the
matter, to GeoServer wms/wcs/wps/ows
are all the same (you can literally use geoserver/workspace/wms to make a
wfs request if you want to,
unless you're forgetting to add =WFS in the URL it should not make
any difference).
E.g.:

http://demo.geo-solutions.it/geoserver/tiger/wms?service=WFS=1.0.0=GetFeature=tiger:tiger_roads=50

And oh, noticed that the preview is indeed using "ows" for WFS, but "wms"
for WMS preview links... LOL :-)

Cheers
Andrea

On Tue, Mar 15, 2016 at 3:19 PM, Andrea Aime 
wrote:

> On Tue, Mar 15, 2016 at 2:38 PM, Damiano Albani 
> wrote:
>
>> Hello,
>>
>> Looking at the content of the GetCapabilities response for WMS, I saw
>> that Request >> OnlineResource URL follows a different pattern than other
>> protocols as WFS and WPS.
>>
>> For example, compare:
>>
>>   http://host/geoserver/workspace/*ows?SERVICE=WMS&*"/>
>>
>>
>>
>>   http://host/geoserver/workspace/*wfs*"/>
>>
>>
>>
>>   http://host/geoserver/workspace/*wps*"/>
>>
>>
>> The last 2 seem more logical / look nicer to me.
>>
>> The implementation for WMS is to be found on
>> https://github.com/geoserver/geoserver/blob/master/src/wms/src/main/java/org/geoserver/wms/capabilities/Capabilities_1_3_0_Transformer.java#L477
>> .
>> To be compared to, say, WFS:
>> https://github.com/geoserver/geoserver/blob/master/src/wfs/src/main/java/org/geoserver/wfs/CapabilitiesTransformer.java#L610
>>
>> What do you think? Shouldn't all protocols follow the same line in term
>> of "canonical" URLs?
>> Or maybe there's a particular (compatibility) reason why WMS is treated
>> differently.
>>
>
> Only because they were developed by different people in different times.
> That said, the "right" version is almost the WMS one,
> it should be using "ows", the service named endpoints wms/wfs/wps and so
> on are kept, as far as I know, for backwards compatibility
> only. It should be "http://host/geoserver/workspace/ows;.
>
> Cheers
> Andrea
>
>
> --
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054  Massarosa (LU)
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39  339 8844549
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
>
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
> darcene notizia via e-mail e di procedere alla distruzione del messaggio
> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
> principi dettati dal D.Lgs. 196/2003.
>
>
>
> The information in this message and/or attachments, is intended solely for
> the attention and use of the named addressee(s) and may be confidential or
> proprietary in nature or covered by the provisions of privacy act
> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
> Code).Any use not in accord with its purpose, any disclosure, reproduction,
> copying, distribution, or either dissemination, either whole or partial, is
> strictly forbidden except previous formal approval of the named
> addressee(s). If you are not the intended recipient, please contact
> immediately the sender by telephone, fax or e-mail and delete the
> information in this message that has been received in error. The sender
> does not give any warranty or accept liability as the content, accuracy or
> completeness of sent messages and accepts no responsibility  for changes
> made after they were sent or for other risks which arise as a result of
> e-mail transmission, viruses, etc.
>
> ---
>



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

Ing. Andrea Aime
@geowolf
Technical Lead

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

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità

Re: [Geoserver-devel] Standardize URL of WMS endpoint in GetCapabilities response

2016-03-15 Thread Andrea Aime 
On Tue, Mar 15, 2016 at 2:38 PM, Damiano Albani 
wrote:

> Hello,
>
> Looking at the content of the GetCapabilities response for WMS, I saw
> that Request >> OnlineResource URL follows a different pattern than other
> protocols as WFS and WPS.
>
> For example, compare:
>
>   http://host/geoserver/workspace/*ows?SERVICE=WMS&*"/>
>
>
>
>   http://host/geoserver/workspace/*wfs*"/>
>
>
>
>   http://host/geoserver/workspace/*wps*"/>
>
>
> The last 2 seem more logical / look nicer to me.
>
> The implementation for WMS is to be found on
> https://github.com/geoserver/geoserver/blob/master/src/wms/src/main/java/org/geoserver/wms/capabilities/Capabilities_1_3_0_Transformer.java#L477
> .
> To be compared to, say, WFS:
> https://github.com/geoserver/geoserver/blob/master/src/wfs/src/main/java/org/geoserver/wfs/CapabilitiesTransformer.java#L610
>
> What do you think? Shouldn't all protocols follow the same line in term of
> "canonical" URLs?
> Or maybe there's a particular (compatibility) reason why WMS is treated
> differently.
>

Only because they were developed by different people in different times.
That said, the "right" version is almost the WMS one,
it should be using "ows", the service named endpoints wms/wfs/wps and so on
are kept, as far as I know, for backwards compatibility
only. It should be "http://host/geoserver/workspace/ows;.

Cheers
Andrea


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

Ing. Andrea Aime
@geowolf
Technical Lead

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

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.



The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

---
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Standardize URL of WMS endpoint in GetCapabilities response

2016-03-15 Thread Damiano Albani 
Hello,

Looking at the content of the GetCapabilities response for WMS, I saw
that Request >> OnlineResource URL follows a different pattern than other
protocols as WFS and WPS.

For example, compare:

  http://host/geoserver/workspace/*ows?SERVICE=WMS&*"/>



  http://host/geoserver/workspace/*wfs*"/>



  http://host/geoserver/workspace/*wps*"/>


The last 2 seem more logical / look nicer to me.

The implementation for WMS is to be found on
https://github.com/geoserver/geoserver/blob/master/src/wms/src/main/java/org/geoserver/wms/capabilities/Capabilities_1_3_0_Transformer.java#L477
.
To be compared to, say, WFS:
https://github.com/geoserver/geoserver/blob/master/src/wfs/src/main/java/org/geoserver/wfs/CapabilitiesTransformer.java#L610

What do you think? Shouldn't all protocols follow the same line in term of
"canonical" URLs?
Or maybe there's a particular (compatibility) reason why WMS is treated
differently.

Regards,

-- 
*Damiano Albani*
Geodan
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Why GetLegendGraphic call in layer publishing tab doesn't use the onlineResource legend?

2016-03-15 Thread Daniele Romagnoli 
Hi list,
I have a couple of questions on the subject since I'm not too familiar with
that and I'm trying to understand how it works.

I have configured a style with a RasterSymbolizer containing a colorMap.
Then, I have set a static legend for that style, referring to a
colormap.png in the GEOSERVER_DATA_DIR/style folder, by configuring the
Online Resource field.
Then, I have configured a raster layer, by specifying that style as default
style.
However, I have noticed that the rendered legend isn't the static one but
it's still the one dynamically computed from the style's colormap.

Is it a bug or is it the expected behaviour?

Taking a look at the code:
https://github.com/geoserver/geoserver/blob/master/src/wms/src/main/java/org/geoserver/wms/legendgraphic/GetLegendGraphicKvpReader.java#L438

It seems like the external legend is only "retrieved" in case the InfoObj
is an instance of a LayerInfo. Debugging there, it is a null object so no
legend is retrieved.

Should the internal getLegendGraphic also provide the LAYER parameter
(since we are in the Publishing tab of a Layer we should know that, right?)?

So, out of curiosity, I have tried passing the LAYER parameter to that
getLegendGraphic but I'm still getting the computed legend instead of the
static one.

Taking a look at the code, I see this:
This line fill the LegendRequest details
https://github.com/geoserver/geoserver/blob/master/src/wms/src/main/java/org/geoserver/wms/legendgraphic/GetLegendGraphicKvpReader.java#L155

This results into calling this:
https://github.com/geoserver/geoserver/blob/master/src/wms/src/main/java/org/geoserver/wms/legendgraphic/GetLegendGraphicKvpReader.java#L234

which setup a FeatureType here:
https://github.com/geoserver/geoserver/blob/master/src/wms/src/main/java/org/geoserver/wms/legendgraphic/GetLegendGraphicKvpReader.java#L235

Note that this line will set the name of the layer as "GridCoverage"
due to using the FeatureUtilities.wrapGridCoverageReader method.
https://github.com/geotools/geotools/blob/master/modules/library/coverage/src/main/java/org/geotools/resources/coverage/FeatureUtilities.java#L221

Long story short, when trying to get the LegendInfo at this line:
https://github.com/geoserver/geoserver/blob/master/src/wms/src/main/java/org/geoserver/wms/legendgraphic/GetLegendGraphicKvpReader.java#L441

will resolve the LegendInfo object but at line 445 it won't get the
LegendRequest:
since the name of the layer doesn't match (being set by the wrapper to
http://www.opengis.net/gml:GridCoverage.)

So I'm lost :-)

Does it represents a set of bugs or did I missed something?
Do you have any feedbacks on the topic?
Please, let me know.

Cheers,
Daniele

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

Ing. Daniele Romagnoli
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.
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration

[Geoserver-devel] [JIRA] (GEOS-7461) After editing/saving a style/layer, plz go back to that style/layer to maybe edit again..

2016-03-15 Thread Richard Duivenvoorde (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Duivenvoorde created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-7461  
 
 
  After editing/saving a style/layer, plz go back to that style/layer to maybe edit again..   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Affects Versions: 
 2.9-beta  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 UI  
 
 
Created: 
 15/Mar/16 10:29 AM  
 
 
Environment: 
 All env  
 
 
Priority: 
  Low  
 
 
Reporter: 
 Richard Duivenvoorde  
 

  
 
 
 
 

 
 Having a Geoserver instance with >100 styles defined, and not being a sld-king. I often have to fix an sld, check the result and (re)fix the sld again. From my (user) standpoint it would be much easier if after the 'save' of the edit we would go back to edited style again, instead of to the long list where I have to use search again to find the style and then click it again to (re)edit. Not sure IF it is an easy fix (not familiar with wicket workflow), but this is one of my longstanding wishes  Making it an option would also be cool off course (given that others probably will want to go back to the list). Same for layer list by the way

[Geoserver-devel] [JIRA] (GEOS-7460) feedback panel / wicket styling

2016-03-15 Thread Richard Duivenvoorde (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Richard Duivenvoorde created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-7460  
 
 
  feedback panel / wicket styling   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Affects Versions: 
 2.9-beta  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 UI  
 
 
Created: 
 15/Mar/16 10:20 AM  
 
 
Priority: 
  Low  
 
 
Reporter: 
 Richard Duivenvoorde  
 

  
 
 
 
 

 
 The green feedback ul when validating a style or reloading server config has a strange space on left size.  Seems trivial to fix, but also creating this issue to 2.9 beta is being used/tested  Will try to add screendump later, currently I receive a "JIRA could not attach the file as there was a missing token. Please try attaching the file again."  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Re: [Geoserver-devel] spring 4 upgrade

2016-03-15 Thread Christian Mueller 
Hi Jody

The CAS test setup is a rather complex one. You have to

1) Create a maven project producing a CAS overlay war file
2) Setup HTTPS  for the server (Generate key on the server side,import
server certificate in cacerts)
3) Setup HTTPS for the client side (CAS server contacts the client using
https for proxy granting tickets).

Maybe the following cold work

Add the overlay CAS war file as test resource.
Search for a free TCP/IP port
Start the war file using Jetty. Jetty must have the proper truststore and
keystore configuration
Start the tests with the proper  truststore and keystore configuration
Shutdown Jetty.

Does this make sense ?

Christian






On Tue, Mar 15, 2016 at 1:02 AM, Jody Garnett 
wrote:

> Thanks Christian, I have updated the wiki page to reflect this progress:
>
> * https://github.com/geoserver/geoserver/wiki/Spring-4-Upgrade
>
> Trying to get a handle on what is left to do, especially testing. If
> security-cas requires any additional testing please add it to the page
> above.
>
> What we have remaining before beta2:
>
> 3. Migrate tests from mock runner to spring-test
>(done) core building
>(done)  extension building
>(volunteer needed) community modules (-PcommunityRelease) could not fix
> everything
>
> 4. GWC - also uses spring and will require update
>(done) Upgrade to Servlet 3.0
>(kevin) Migrate from Acegi 1.0.7 to Spring Security
>
> 5. GeoFence Integration
>(volunteer) needed
>
> 7. community modules (-PcommunityRelease)
>need a list of these
>
> 8. Merge feature branch, release 2.9-beta2
>
>
> --
> Jody Garnett
>
> On 13 March 2016 at 09:01, Christian Mueller <
> christian.muel...@os-solutions.at> wrote:
>
>> Hi
>>
>> I have do done the the CAS Port and pushed the commit to
>>  the spring4-upgrade branch.
>>
>> Cheers
>>
>>
>> On Sun, Mar 13, 2016 at 5:20 AM, Jody Garnett 
>> wrote:
>>
>>> Do not worry about login/logout for GeoExplorer.
>>>
>>> However I think the endpoint may be used by others so we should supply
>>> migration instructions for anyone else affected.
>>>
>>>
>>>
>>>
>>> On Sat, Mar 12, 2016 at 12:32 PM Justin Deoliveira 
>>> wrote:
>>>
 An update on this one.

 Basically where it stands is that I think everything minus CAS has been
 ported over the new spring apis and afaik all tests are passing. I’ve run
 the server (with just the core modules) and can confirm that a quick smoke
 test doesn’t show any problems.

 In terms of compability issues the only issue I have found thus far is
 the issue with the spring security login endpoints changing (ie.
 /j_spring_security_check is now /login). It’s on my list to circle back to
 see if we can somehow change some config to use the old paths. However when
 I looked before it didn’t look possible. I only know of one application
 (GeoExplorer) that utilizes the endpoints to login so i am not sure how far
 reaching this issue actually is.

 So off the top of my head the remaining tasks are:

 - Port CAS
 - Look at the login/logout endpoint issue
 - Decide what to do about the login/logout issue if we can’t change
 them back
 - Do some more general and thorough testing



 On Fri, Mar 4, 2016 at 12:19 PM Jody Garnett 
 wrote:

> Thanks Christian, I will write up the blog post - and talk to you all
> next week with respect to planning.
>
> --
> Jody Garnett
>
> On 3 March 2016 at 23:24, Christian Mueller <
> christian.muel...@os-solutions.at> wrote:
>
>> Hi all
>>
>> I think it is necessary to upgrade, +1 here. I have seen Justin
>> created a branch spring4-upgrade fixing the broken security code.
>>
>> For CAS I have an online test scenario.
>>
>> Cheers
>>
>>
>>
>> On Thu, Mar 3, 2016 at 6:19 PM, Jody Garnett 
>> wrote:
>>
>>> Thanks Simone, updating the page. I will give Christian another day
>>> and then I would like to start making plans.
>>>
>>> --
>>> Jody Garnett
>>>
>>> On 3 March 2016 at 09:16, Simone Giannecchini <
>>> simone.giannecch...@geo-solutions.it> wrote:
>>>
 Ciao Jody,
 I am for upgrading to Spring 4 + delaying the release.

 I already told Andrea we can devote resources to help with the
 upgrade.


 Regards,
 Simone Giannecchini
 ==
 GeoServer Professional Services from the experts!
 Visit http://goo.gl/it488V for more information.
 ==
 Ing. Simone Giannecchini
 @simogeo
 Founder/Director

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