[Geoserver-devel] [JIRA] (GEOS-8145) Cascading WMS does not allow long credentials

2017-05-18 Thread Lorenzo Pini (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lorenzo Pini created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-8145  
 
 
  Cascading WMS does not allow long credentials   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 2.6.2, 2.10.0, 2.10.3  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 WMS  
 
 
Created: 
 18/May/17 9:40 PM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Lorenzo Pini  
 

  
 
 
 
 

 
 Due to GEOT-5731 a cascading WMS store cannot be configured if the combined username and password lenght is too big. To reproduce: 
 
Go to "Add New Store" -> "WMS - Cascades a remote Web Map Service" 
insert random name and url 
insert long username 
insert long password 
save 
 

 
org.apache.wicket.WicketRuntimeException: Exception 'Illegal character(s) in message header value: Basic dmVlZWVlZWVlZWVlZWVlZWVlZXJycnJycnJycnl5eXl5eXl5eXl5eXl5eXlsb29vb29vb29vb29v bmc6cGFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFh YWFhYWFhYWFhc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzd3d3d3d3d3d3d3d3d3d3d3d3d3d3 d3d3d3d3d29yZA==' occurred during validation org.geoserver.web.data.store.WMSStoreNewPage$WMSCapabilitiesURLValidator on component 7:form:capabilitiesURL:border:border_body:paramValue at org.apache.wicket.markup.html.form.FormComponent.validateValidators(FormComponent.java:1529) at 

[Geoserver-devel] [JIRA] (GEOS-8129) GetLegendGraphic fails if SCALE is greater than MaxScaleDenominator

2017-05-08 Thread Lorenzo Pini (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lorenzo Pini created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-8129  
 
 
  GetLegendGraphic fails if SCALE is greater than MaxScaleDenominator   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 2.10.4  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 08/May/17 2:27 PM  
 
 
Environment: 
 Linux 64bit, Java Oracle 1.8.0, Tomcat 7, GeoServer 2.10-snapshot ( 70b43aa9e8d6d3f6576a73620a9dc5821febb2ad ) DuctusRenderingEngine No JAI  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Lorenzo Pini  
 

  
 
 
 
 

 
 If a style has a Rule with  and no other rule to match scales over it, the GetLegendGraphic fails with an Exception when a greater scale is requested. Example, all the rules in the style "poi" have 32000 If the requested scale matches the limit, it gives you an image: http://demo.geo-solutions.it/geoserver/wms?service=WMS=GetLegendGraphic=image%2Fpng=12=12=tiger%3Apoi==1.3.0_VERSION=1.1.0=32000 Otherwise an Exception: http://demo.geo-solutions.it/geoserver/wms?service=WMS=GetLegendGraphic=image%2Fpng=12=12=tiger%3Apoi==1.3.0_VERSION=1.1.0=32001 

 

"http://www.opengis.net/ogc" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.3.0" xsi:schemaLocation="http://www.opengis.net/ogc http://demo.geo-solutions.it:80/geoserver/schemas/wms/1.3.0/exceptions_1_3_0.xsd">

java.lang.IllegalArgumentException: Width (2) and height (0) must be > 0 Width (2) and height (0) must be > 0


 

 Logs the following: 

 

[Geoserver-devel] [JIRA] (GEOS-8060) Wicket error reloading feature type from JNDI

2017-03-31 Thread Lorenzo Pini (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lorenzo Pini created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-8060  
 
 
  Wicket error reloading feature type from JNDI   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 2.9.5  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Wicket UI  
 
 
Created: 
 31/Mar/17 11:45 AM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Lorenzo Pini  
 

  
 
 
 
 

 
 A layer is published froma Oracle NG (JNDI) store. The layer is disabled Click on "Reload feature type", nothing happen Click on the Warning icon on the right of "Reload feature type", a warning message appears. Close the popup, the following message is shown. 

 

java.lang.RuntimeException: Could not deserialize object from byte[]
	at org.apache.wicket.serialize.java.JavaSerializer.deserialize(JavaSerializer.java:143)
	at org.apache.wicket.pageStore.AbstractPageStore.deserializePage(AbstractPageStore.java:152)
	at org.apache.wicket.pageStore.AbstractCachingPageStore.getPage(AbstractCachingPageStore.java:67)
	at org.apache.wicket.page.PageStoreManager$SessionEntry.getPage(PageStoreManager.java:203)
	at org.apache.wicket.page.PageStoreManager$PersistentRequestAdapter.getPage(PageStoreManager.java:357)
	at org.apache.wicket.page.AbstractPageManager.getPage(AbstractPageManager.java:82)
	at org.apache.wicket.page.PageManagerDecorator.getPage(PageManagerDecorator.java:50)
	at org.apache.wicket.page.PageAccessSynchronizer$2.getPage(PageAccessSynchronizer.java:246)
	at org.apache.wicket.DefaultMapperContext.getPageInstance(DefaultMapperContext.java:113)
	at org.apache.wicket.core.request.handler.PageProvider.getStoredPage(PageProvider.java:299)
	at 

[Geoserver-devel] [JIRA] (GEOS-7452) Process Status page do not refresh after a dismiss

2016-03-09 Thread Lorenzo Pini (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lorenzo Pini created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-7452  
 
 
  Process Status page do not refresh after a dismiss   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 2.8.2  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Wicket UI  
 
 
Created: 
 09/Mar/16 3:51 PM  
 
 
Environment: 
 GeoServer 2.8.2 with WPS and MBTiles plugins Chrome Browser  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Lorenzo Pini  
 

  
 
 
 
 

 
 Hi, I started an MBTiles process and let it run for a while. When I wanted to dismiss it I went to the "Process Status" page in the GeoServer web UI. The process was dismissed but the page did not refresh. I had to reload the page to see the empty processes list To reproduce: Start a WPS process Open the "Process Status" page  Select a process and click "Dismiss selected processes" Confirm the dismiss. The expected behaviour is: The process list is updated without the dismised process The current behaviour is: The process list is not reloaded.  
 

  
 
 
 
 

 
 
 

 
  

[Geoserver-devel] [JIRA] (GEOS-7342) LayerGroup chooser in the LayerGroup page suggests LGs from other workspaces

2015-12-11 Thread Lorenzo Pini (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lorenzo Pini created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-7342  
 
 
  LayerGroup chooser in the LayerGroup page suggests LGs from other workspaces   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Affects Versions: 
 2.6.3  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Wicket UI  
 
 
Created: 
 11/Dec/15 4:47 PM  
 
 
Labels: 
 LayerGroup Workspace  
 
 
Priority: 
  Low  
 
 
Reporter: 
 Lorenzo Pini  
 

  
 
 
 
 

 
 Use case: Create a workspace "A" Create a Layer Group "LGA" (in workspace A) Create a workspace "B" Create a Layer Group "LGB" Select workspace B Select "Add Layer Group..." The LGA layergroup is displayed and can be selected Save The Save fails with the error: Layer group within a workspace (B) can not contain resources from other workspace: A  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  

[Geoserver-devel] [JIRA] (GEOS-7220) Document GetFeatureInfo on layergroup

2015-09-28 Thread Lorenzo Pini (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lorenzo Pini created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 GeoServer /  GEOS-7220 
 
 
 
  Document GetFeatureInfo on layergroup  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Documentation 
 
 
 

Created:
 

 28/Sep/15 3:33 PM 
 
 
 

Priority:
 
  Low 
 
 
 

Reporter:
 
 Lorenzo Pini 
 
 
 
 
 
 
 
 
 
 
Document GetFeatureInfo behaviour on layergroups. Related to GEOS-6340 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.0-OD-07-011#70107-sha1:db940e9) 
   

[Geoserver-devel] [JIRA] (GEOS-7106) WFS DescribeFeatureType NPE with misconfigured layers

2015-07-14 Thread Lorenzo Pini (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lorenzo Pini created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 GeoServer /  GEOS-7106 
 
 
 
  WFS DescribeFeatureType NPE with misconfigured layers  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 2.6.4 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 WFS 
 
 
 

Created:
 

 14/Jul/15 1:29 PM 
 
 
 

Environment:
 
 
Version 2.6.4 Git Revision e522cb760457751b496e42b1169f8a344f934849  Running on Tomcat 6 Java OpenJDK 64-Bit Server VM 1.7.0_79 
 
 
 

Priority:
 
  Low 
 
 
 

Reporter:
 
 Lorenzo Pini 
 
 
 
 
 
 
 
 
 
 
An SQL View can be configured to have spaces in the Attributes names.  WFS DescribeFeatureType call fails with a java.lang.NullPointerException on such layers. 
To reproduce, create an SQL View with aliases and spaces names: 

 
SELECT prop1 AS Prop with spaces, geom  from my_table;
 

 
Publish 

[Geoserver-devel] [JIRA] (GEOS-7082) WFS Content-Type cannot include charset

2015-06-19 Thread Lorenzo Pini (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lorenzo Pini created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 GeoServer /  GEOS-7082 
 
 
 
  WFS Content-Type cannot include charset  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 2.6.4 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 WFS 
 
 
 

Created:
 

 19/Jun/15 5:01 PM 
 
 
 

Environment:
 
 
Debian 7 wheezy Tomcat 6.0.41 GeoServer 2.6.4 AuthKey plugin WPS plugin Excel plugin 
 
 
 

Priority:
 
  Medium 
 
 
 

Reporter:
 
 Lorenzo Pini 
 
 
 
 
 
 
 
 
 
 
The requests issued to the WFS service with the  Content-Type: application/x-www-form-urlencoded; charset=UTF-8 header are not recognized as form and parsed as XML resulting in a failure. 
Answer is: 

 
  ows:Exception exceptionCode=NoApplicableCode
ows:ExceptionTextorg.xmlpull.v1.XmlPullParserException: only whitespace content allowed before start tag and not s (position: START_DOCUMENT seen s... @1:1)
only whitespace content allowed before start tag and not s (position: 

[Geoserver-devel] [jira] (GEOS-6899) Filter Chain Editing does not work

2015-02-20 Thread Lorenzo Pini (JIRA)
Title: Message Title










 

 Lorenzo Pini created an issue


















 GeoServer /  GEOS-6899



  Filter Chain Editing does not work 










Issue Type:

  Bug




Affects Versions:


 2.6.2




Assignee:

 Andrea Aime




Components:


 Security




Created:


 20/Feb/15 8:53 AM




Labels:


 security authentication authorization




Priority:

  Major




Reporter:

 Lorenzo Pini










In the Filter Chain page ( geoserver/web/?wicket:interface=:87 ) I'm trying to set up a new Chain filter by moving it from the Available box to the Selected box.
In the interface it works and a POST is sent with the correct values and ordering: authFilterChain:recorder geostore,basic,anonymous
After the change GeoServer does not react as expected and inspecting the security/config.xml file I see that the geostore filter is missing.
... filters name=default class=org.geoserver.security.ServiceLoginFilterChain interceptorName=interceptor exceptionTranslationName=exception path=/** disabled=false allowSessionCreation=false ssl=false matchHTTPMethod=false filterbasic/filter filteranonymous/filter /filters ...
   

[Geoserver-devel] [jira] (GEOS-6798) Saving layer after an SQL view edit causes WicketRuntimeException

2014-12-11 Thread Lorenzo Pini (JIRA)
Title: Message Title










 

 Lorenzo Pini created an issue


















 GeoServer /  GEOS-6798



  Saving layer after an SQL view edit causes WicketRuntimeException 










Issue Type:

  Bug




Affects Versions:


 2.4.8




Assignee:

 Andrea Aime




Components:


 Wicket UI




Created:


 11/Dec/14 10:07 AM




Environment:


 CentOS 6  GeoServer 2.4.8  JAVA: Oracle Corporation: 1.7.0_65 (OpenJDK 64-Bit Server VM)




Priority:

  Minor




Reporter:

 Lorenzo Pini










I had an SQL view without an identifier, so I edited the SQL statement to include another field and setted it as Identifier. The Edit SQL view page save when fine. The Edit Layer page save returned this stack trace.
Reopening the layer showed no problem, the data was updated correcly.
org.apache.wicket.WicketRuntimeException: Method onFormSubmitted of interface org.apache.wicket.markup.html.form.IFormSubmitListener targeted at component [MarkupContainer [Component id = resource]] threw an exception at org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:193) at