[Geoserver-devel] Reminder: GeoTools / GeoServer Meeting at 17:30 UTC on Tuesday
GeoTools / GeoServer committee meeting on Skype at 17:30 UTC on Tuesday: http://www.timeanddate.com/worldclock/meetingdetails.html?year=2015month=2day=3hour=17min=30sec=0p1=256p2=215p3=101p4=952 Andrea Aime wrote: 1. meeting time --- 18:30 CET time 9:30 PST time -- Ben Caradoc-Davies b...@transient.nz Software Engineer Transient Software http://transient.nz New Zealand -- Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] proposal: Layer with Service Security
Niels are you available for the geoserver meeting tomorrow? I managed to catch up with the email thread. While I like the idea of extending the text-file approach (and you have been clever in figuring out a format) the result is quite confusing. I would also like to look at what is needed for GeoFence to become supported. -- Jody On Tue, Jan 20, 2015 at 6:53 AM, Niels Charlier ni...@scitus.be wrote: Hello Group, There has been a request to allow a basic combination of layer and service security in the integrated geoserver security subsystem. I have made a proposal to that end: https://github.com/geoserver/geoserver/wiki/GSIP-125---Layer-with-Service-Security In summary, the proposal is to extend layer security to support service/operation specificity and leave the existing service security intact. As you can see in the proposal there is still a discussion to be had as to how certain rules will interact, but I have made a suggestion for what I think is the most logical solution. Please offer me your feedback. Kind Regards NIels -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel -- -- Jody Garnett Technical Lead | Boundless http://boundlessgeo.com/ jgarn...@boundlessgeo.com http://mailto:jgarn...@boundlessgeo.com/ 877-673-6436 @jodygarnett https://twitter.com/jodygarnett [image: http://boundlessgeo.com/] http://boundlessgeo.com/ -- Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GWC and workspace specific styles
Yes my plan was ultimately to hide the Workspace parameter and have the filter added and updated automatically the way the style filter is so it would all be transparent to the user. I don't think you're missing anything, I just wanted to make sure workspace renames were covered. On 2 February 2015 at 12:44, Andrea Aime andrea.a...@geo-solutions.it wrote: On Mon, Feb 2, 2015 at 8:31 PM, Kevin Smith ksm...@boundlessgeo.com wrote: I was looking at the same two problems in a different way. I'd considered the prefix route on styles but hadn't noticed that solution to the LayerGroups issue and wanted to solve both. So I ended up working on improving the workspace parameter filter option instead, which lead to some improvements in GWC I'm still working on, specifically GWC ticket #170. The work I did should still be able to simplify the Style filter and make it more robust, while also making other new parameter filters with similarly dynamic behaviour easier to write and generally helping to avoid 'leaking' of parameterized tile caches, particular when using the RexExp filter. I don't think my route would have been backportable, and would have been a stretch to make it into GWC 1.7.x/GS 2.7.x now that we are beta so, even though it sort of obsoletes what I've been working on for the past few days, I'm glad to see this. I did not try to make the work backportable either (not with that intention at least), but I find the workspace parameter... ugh GWC integration must be transparent, it's the primary feature of the integrated GW, a solution that breaks it is imho no solution, but a temporary band-aid in user's face (e.g., exactly where it should not be, band aids are ugly, but if needs be, better hide them under the carpet). Yes my plan was ultimately to hide the Workspace parameter and have the filter added and updated automatically the way the style filter is so it would all be transparent to the user. The backportability issues I had with my solution were that it involved API changes in GWC: BlobStoreListener ended up with a new event to handle parameterizations being purged. I wasn't happy with either of trying to put it in 1.7 this late or waiting for 1.8. Since your solution is much less intrusive and confined to GS, it should be able to make GS 2.7 and my parameterization purge/dynamic param filter work can go into GWC 1.8. I see your comments about moving the workspace, did not consider it in fact (2.5 hours hack on a Sunday morning... that's why I asked for a review :-p ), but I don't see a problem taking it into account in a similar way to how we consider workspace name changes in layers... am I missing something? I just wanted to make sure that case was covered but I don't think it presents any particular issues to your approach. It was one of the rare but annoying special cases that made my approach complicated. -- Kevin Smith Software Engineer | Boundless http://boundlessgeo.com/ ksm...@boundlessgeo.com +1-778-785-7459 @boundlessgeo http://twitter.com/boundlessgeo/ http://twitter.com/boundlessgeo/ [image: http://boundlessgeo.com/] http://boundlessgeo.com/ -- Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GWC and workspace specific styles
On Mon, Feb 2, 2015 at 8:31 PM, Kevin Smith ksm...@boundlessgeo.com wrote: I was looking at the same two problems in a different way. I'd considered the prefix route on styles but hadn't noticed that solution to the LayerGroups issue and wanted to solve both. So I ended up working on improving the workspace parameter filter option instead, which lead to some improvements in GWC I'm still working on, specifically GWC ticket #170. The work I did should still be able to simplify the Style filter and make it more robust, while also making other new parameter filters with similarly dynamic behaviour easier to write and generally helping to avoid 'leaking' of parameterized tile caches, particular when using the RexExp filter. I don't think my route would have been backportable, and would have been a stretch to make it into GWC 1.7.x/GS 2.7.x now that we are beta so, even though it sort of obsoletes what I've been working on for the past few days, I'm glad to see this. I did not try to make the work backportable either (not with that intention at least), but I find the workspace parameter... ugh GWC integration must be transparent, it's the primary feature of the integrated GW, a solution that breaks it is imho no solution, but a temporary band-aid in user's face (e.g., exactly where it should not be, band aids are ugly, but if needs be, better hide them under the carpet). I see your comments about moving the workspace, did not consider it in fact (2.5 hours hack on a Sunday morning... that's why I asked for a review :-p ), but I don't see a problem taking it into account in a similar way to how we consider workspace name changes in layers... am I missing something? Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy 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. --- -- Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] windows build server failures on master
Yes, it checks if the file at the absolute path exists and if not assumes the path is relative. You could swap the order making the relative path default. Fail? The tests use paths to files that does not exist. The result will be that the path to the file will be relative. And that's the same result that you get on other platforms. But yes, if your intention is to use an absolute path to something that does not exist yet it will fail. So, by swapping the order you would get the absoulte file path as the default on windows as before for files that do not exist yet. But if there is a file there for the relative case that will be used instead. However that seems a bit unlikely. Should I update the PR to do that? Still not sure how the Java Path API would help here. /Olle On Sun, Feb 1, 2015 at 11:26 PM, Jody Garnett jody.garn...@gmail.com wrote: One of the lines in your pull request uses the test if (!f.exists()) This only works if the DataUtilities.urlToFile method is referring to a file that has been created yet. If we try the same logic on a file that does not exist yet it will fail... -- Jody Garnett On 1 February 2015 at 06:36, Olle Markljung marklj...@gmail.com wrote: Sorry for the delay. Ticket: http://jira.codehaus.org/browse/GEOT-4990 PR: https://github.com/geotools/geotools/pull/717 This builds clean using mvn clean install on my machine (building geotools). Should I communicate this on the geotools list as well? Not sure that I understand what you mean Jody. If I have gotten this right the problem is to know if the user provide an absolute or relative path. How would the path API help in knowing the intentions of the user? /Olle On Wed, Jan 21, 2015 at 12:33 AM, Jody Garnett jody.garn...@gmail.com wrote: Sounds like a good approach - we may also be able to use Java 7 Path API. I should also point out that we may be using this to figure out a the location of a *new* file (like one that does not exist yet). Perhaps the Java 7 path api can help. -- Jody -- Jody Garnett On 20 January 2015 at 15:28, Olle Markljung marklj...@gmail.com wrote: Ok, Perhaps it is not easy to say in what ways it all should work. Someone ought to be depending on the code doing this specific thing on Windows since the code exists. So, I got a proposition. What if we in DataUtilities.urlToFile do the same as DefaultResourceLocator.locateResource already does. That is to check if the file exists. If it doesn't we remove the extra slashes and makes the URI relative. I extended the tests and added such code to the Windows specific case and it works as expected. Should I create a ticket and send a PR with these changes for your review? /Olle On Mon, Jan 19, 2015 at 11:42 PM, Olle Markljung marklj...@gmail.com wrote: Ok. Looking at the history I can't find anything that changed. Version of Java did change to 7. These urls also fail in GeoTools. It's not the usage of urlToFile in the test that's the problem but the usage of urlToFile in the DefaultResourceLocator.locateResource. The file:// is converted to // by urlToFile and this means it's not relative. You'll get the same behavior if you use file:/ instead. Therefore locateResource will leave the URI as is and not make it relative to the styles folder. So, on Windows the urls will be interpreted as absolute but on other platforms it will be relative. Atleast the file:// case. Should file://host/share/dest.png be supported on Windows but not elsewhere? Would \\host\share\dest.png work an be a acceptable replacement? Is it intentional that file:/ will be an absolute path and file:// not? Something that does work is removing the forward slashes. So, file:dest.png will give you the correct behavior. As https://jira.codehaus.org/browse/GEOT-4311 says. I'm merely trying to understand the requirements so go easy on me :) /Olle On Mon, Jan 19, 2015 at 9:40 AM, Andrea Aime andrea.a...@geo-solutions.it wrote: On Mon, Jan 19, 2015 at 9:29 AM, Olle Markljung marklj...@gmail.com wrote: Yes, I see now that I was a bit unclear with my intentions of the last paragraph. However, I believe that the usage of the file protocol makes it unclear as when the file path will be interpreted as relative over absolute. I can get back to you with some exemples and maybe we can document the requirements and expected behavior. The test is checking for behavior that was working up to 2.5.x. Both worked: file://dest.png file.//./dest.png Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy 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
Re: [Geoserver-devel] windows build server failures on master
Since (in GeoServer) we try to discourage the use of absolute paths I guess I am fine with the way things stand. If we were just focused on manipulating the file path in a safe manner the Java Paths API would help (since we actually want to check a file on disk I expect the Files API is fine). Correct me if I am wrong, and absolute path on windows will end up using the C:\ notation or the \\host\share\ notation - in both cases these are pretty specific and not confusable as a relative path? -- Jody Garnett On 2 February 2015 at 14:52, Olle Markljung marklj...@gmail.com wrote: Yes, it checks if the file at the absolute path exists and if not assumes the path is relative. You could swap the order making the relative path default. Fail? The tests use paths to files that does not exist. The result will be that the path to the file will be relative. And that's the same result that you get on other platforms. But yes, if your intention is to use an absolute path to something that does not exist yet it will fail. So, by swapping the order you would get the absoulte file path as the default on windows as before for files that do not exist yet. But if there is a file there for the relative case that will be used instead. However that seems a bit unlikely. Should I update the PR to do that? Still not sure how the Java Path API would help here. /Olle On Sun, Feb 1, 2015 at 11:26 PM, Jody Garnett jody.garn...@gmail.com wrote: One of the lines in your pull request uses the test if (!f.exists()) This only works if the DataUtilities.urlToFile method is referring to a file that has been created yet. If we try the same logic on a file that does not exist yet it will fail... -- Jody Garnett On 1 February 2015 at 06:36, Olle Markljung marklj...@gmail.com wrote: Sorry for the delay. Ticket: http://jira.codehaus.org/browse/GEOT-4990 PR: https://github.com/geotools/geotools/pull/717 This builds clean using mvn clean install on my machine (building geotools). Should I communicate this on the geotools list as well? Not sure that I understand what you mean Jody. If I have gotten this right the problem is to know if the user provide an absolute or relative path. How would the path API help in knowing the intentions of the user? /Olle On Wed, Jan 21, 2015 at 12:33 AM, Jody Garnett jody.garn...@gmail.com wrote: Sounds like a good approach - we may also be able to use Java 7 Path API. I should also point out that we may be using this to figure out a the location of a *new* file (like one that does not exist yet). Perhaps the Java 7 path api can help. -- Jody -- Jody Garnett On 20 January 2015 at 15:28, Olle Markljung marklj...@gmail.com wrote: Ok, Perhaps it is not easy to say in what ways it all should work. Someone ought to be depending on the code doing this specific thing on Windows since the code exists. So, I got a proposition. What if we in DataUtilities.urlToFile do the same as DefaultResourceLocator.locateResource already does. That is to check if the file exists. If it doesn't we remove the extra slashes and makes the URI relative. I extended the tests and added such code to the Windows specific case and it works as expected. Should I create a ticket and send a PR with these changes for your review? /Olle On Mon, Jan 19, 2015 at 11:42 PM, Olle Markljung marklj...@gmail.com wrote: Ok. Looking at the history I can't find anything that changed. Version of Java did change to 7. These urls also fail in GeoTools. It's not the usage of urlToFile in the test that's the problem but the usage of urlToFile in the DefaultResourceLocator.locateResource. The file:// is converted to // by urlToFile and this means it's not relative. You'll get the same behavior if you use file:/ instead. Therefore locateResource will leave the URI as is and not make it relative to the styles folder. So, on Windows the urls will be interpreted as absolute but on other platforms it will be relative. Atleast the file:// case. Should file://host/share/dest.png be supported on Windows but not elsewhere? Would \\host\share\dest.png work an be a acceptable replacement? Is it intentional that file:/ will be an absolute path and file:// not? Something that does work is removing the forward slashes. So, file:dest.png will give you the correct behavior. As https://jira.codehaus.org/browse/GEOT-4311 says. I'm merely trying to understand the requirements so go easy on me :) /Olle On Mon, Jan 19, 2015 at 9:40 AM, Andrea Aime andrea.a...@geo-solutions.it wrote: On Mon, Jan 19, 2015 at 9:29 AM, Olle Markljung marklj...@gmail.com wrote: Yes, I see now that I was a bit unclear with my intentions of the last paragraph. However, I believe that the usage of the file protocol makes it unclear as when the file path will be interpreted as relative over absolute. I can get back to you with some exemples and maybe we can document the
[Geoserver-devel] [jira] (GEOS-6866) how to use GeoWebCache
Title: Message Title Kevin Shah created an issue GeoServer / GEOS-6866 how to use GeoWebCache Issue Type: Bug Affects Versions: 2.5 Assignee: Andrea Aime Components: WMS Created: 02/Feb/15 6:41 AM Environment: GeoWebCache Priority: Major Reporter: Kevin Shah Hello Guys, I am facing issue related to GeoWebCache. I want to generate tile images for the layers that I am use to render map using WMS request from Thinkgeo. Now I have Geoserver is some other machine and application that use map is on another location so it takes long time to render the map using WMS request so I have search for Tile caching and I come to know that using GeoWebCache I can do this. I have make change in Layer as well done some change for enable caching and generate Seed for the layer to do caching. Now I have Layergroup to render the map in application. how I can use this cache in my application what should be URL and expected parameters for that.? I have use EPSG:3857 for my layers and also create
[Geoserver-devel] Build failed in Jenkins: geoserver-2.6.x-nightly #174
See http://ares.opengeo.org/jenkins/job/geoserver-2.6.x-nightly/174/changes Changes: [andrea.aime] [GEOS-6867] Filter validation fails in WFS when a join needs to be reordered, and has local, non joining filters -- [...truncated 2754 lines...] [INFO] BeanShell Scripting Extension . SKIPPED [INFO] Ruby Scripting Extension .. SKIPPED [INFO] Application Schema Support SKIPPED [INFO] Application Schema Integration Test ... SKIPPED [INFO] Sample DataAccess Integration Test SKIPPED [INFO] ArcSDE DataStore Extension SKIPPED [INFO] GeoSearch Index Module SKIPPED [INFO] SQL Server DataStore Extension SKIPPED [INFO] Oracle DataStore Extension SKIPPED [INFO] MySQL DataStore Extension . SKIPPED [INFO] DB2 DataStore Extension ... SKIPPED [INFO] ImageMap Output Format SKIPPED [INFO] ImageI/O-Ext GDAL Coverage Extension .. SKIPPED [INFO] JP2K Coverage Extension ... SKIPPED [INFO] ogr2ogr Output Format . SKIPPED [INFO] Excel Output Format ... SKIPPED [INFO] Chart external graphics support ... SKIPPED [INFO] Feature Generalization Extension .. SKIPPED [INFO] Image Mosaic JDBC Extension ... SKIPPED [INFO] OWS request flow controller ... SKIPPED [INFO] Web Processing Service GUI SKIPPED [INFO] GeoServer Layer Querying filter functions . SKIPPED [INFO] Teradata DataStore Extension .. SKIPPED [INFO] GeoServer Monitor Extensions .. SKIPPED [INFO] Core Monitor Extension SKIPPED [INFO] Monitor Hibernate Extension ... SKIPPED [INFO] GeoServer Security Extension Modules .. SKIPPED [INFO] GeoServer CAS Security Module . SKIPPED [INFO] GeoServer Security Extension Web Modules .. SKIPPED [INFO] GeoServer CAS Security Web Module . SKIPPED [INFO] XLST based WFS output format .. SKIPPED [INFO] GeoServer INSPIRE Extensions .. SKIPPED [INFO] GeoServer CSS Styling . SKIPPED [INFO] Catalog Services for the Web parent ... SKIPPED [INFO] Catalog Services for the Web interfaces ... SKIPPED [INFO] Catalog Services for the Web - Simple CatalogStore implementation SKIPPED [INFO] Catalog Services for the Web core module .. SKIPPED [INFO] CSW UI Module . SKIPPED [INFO] DXF WFS output format and WPS PPIO SKIPPED [INFO] DXF WFS output format . SKIPPED [INFO] DXF WPS PPIO .. SKIPPED [INFO] Printing Module ... SKIPPED [INFO] GeoServer WCS 2.0 Earth Observation Extensions SKIPPED [INFO] Web Coverage Service 2.0 Earth Observation extensions SKIPPED [INFO] Web Coverage Service 2.0 Earth Observation GUI extension SKIPPED [INFO] GeoServer libjpeg-turbo Module SKIPPED [INFO] GeoServer Data Importer ... SKIPPED [INFO] Importer Core Module .. SKIPPED [INFO] Importer REST Api Module .. SKIPPED [INFO] Importer Berkley DB Persistence Module SKIPPED [INFO] Importer Web UI Module SKIPPED [INFO] GeoServer Release Module .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 3:01.026s [INFO] Finished at: Tue Feb 03 04:22:14 UTC 2015 [INFO] Final Memory: 51M/213M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project gs-gwc: Compilation failure: Compilation failure: [ERROR] http://ares.opengeo.org/jenkins/job/geoserver-2.6.x-nightly/ws/src/gwc/src/main/java/org/geoserver/gwc/GWC.java:[83,32] error: package org.geowebcache.diskquota does not exist [ERROR] http://ares.opengeo.org/jenkins/job/geoserver-2.6.x-nightly/ws/src/gwc/src/main/java/org/geoserver/gwc/GWC.java:[84,32] error: package org.geowebcache.diskquota does not exist [ERROR] http://ares.opengeo.org/jenkins/job/geoserver-2.6.x-nightly/ws/src/gwc/src/main/java/org/geoserver/gwc/GWC.java:[85,32] error: package org.geowebcache.diskquota does not exist [ERROR]
Re: [Geoserver-devel] Regression in 2.7.x, valid coverage names are rejected because not valid xml names
Hi, Wanted to throw a little experience we had with names and how we solved them; We have an upload capability with our application for users with specific roles to upload a zipped shape file for inclusion with the catalog via ingestion to a PostGIS database. Our initial use case when learning GeoServer was all WMS calls. When we began to experiment with WFS returns via GML and GeoJSON, we found the issue with the names. Because the potential exists for the data returning via WFS and may be used for WFS-T updates, we had to ensure the names were valid XML element names. We found out through trial and error that the layer name had to be XML consistent while learning how to call WFS-T for updates to previously uploaded shapes. Error messages returned indicated the source of the problem. I suspect that many new geospatial developers find out the naming requirements this way. Our Solution: We implemented a layer verification step for administrators to provide a layer name, security roles, etc. before the layer is actually added to the GeoServer catalog via REST calls. During the verification phase, the proposed name provided by the administrator is checked for XML consistency as well as uniqueness within the catalog. If the name is not valid for XML, we display the appropriate error message. If the name is not unique, we append a 1, 2, 3 etc. to the end of the name ensuring the name is unique both as a test as well as during the actual save call in cases of race condition upon verification. I agree that fixing layer names is the responsibility of the administrator and the application attempting to help by automatically renaming or hiding the layers overall is a bad thing. It would not be very pleasant to the end user when a layer they were expecting disappears from the dynamic catalog. By the same token, the portions of GeoServer that are sensitive to the name requirements already appear to provide proper error messages for an administrator or end client application developer to make corrections. Regarding the original error message and use case that Andrea reported, the application has specific use cases that worked until GeoServer was updated in an attempt to solve a problem that didn't even exist. The application developers already know whether their use of GeoServer will utilize XML generated output or require XML updates via WFS-T and generate the layer naming convention based on their use. Enforcing a particular naming requirement is the responsibility of the client/administering application, even if it is GeoServer Web UI. In the case of the GeoServer UI, checks can be put in place for the name when adding or updating a layer on the Edit Layer screen with a warning message when a name is not applicable for particular uses cases such as WFS. The layers listing screen can be updated to add a warning message next to the layer name indicating when the name is not valid for WFS. My .03... Thanks, Chris Snider Senior Software Engineer Intelligent Software Solutions, Inc. [Description: Description: Description: cid:image001.png@01CA1F1F.CBC93990] From: Rahkonen Jukka (MML) [mailto:jukka.rahko...@maanmittauslaitos.fi] Sent: Saturday, January 31, 2015 3:17 AM To: Jody Garnett; Andrea Aime Cc: Geoserver-devel Subject: Re: [Geoserver-devel] Regression in 2.7.x, valid coverage names are rejected because not valid xml names Based on the 29 open tickets which deal with non-simple resource names we have real issues with them. Could we at least try to emphasize in the documentation and perhaps with some warning in the GUI that using such names calls for troubles? -Jukka Rahkonen- Jody Garnett wrote: I am uncomfortable with the idea of silently disabling feature type layers - if the user has turned on both WFS and WMS publication. This proposal has drifted too far from my original goals. I will mark it withdrawn and focus on fixing the style names in isolation. -- Jody Garnett On 30 January 2015 at 13:33, Jody Garnett jody.garn...@gmail.commailto:jody.garn...@gmail.com wrote: So we are left with the question of how to notify admins for layers that are disabled for a specific service. As for the styles name change (damage is currently already done and is affecting ability to upgrade) we can either allow the invalid characters (with a warning) or watch them fail. -- Jody -- Jody Garnett On 30 January 2015 at 13:05, Andrea Aime andrea.a...@geo-solutions.itmailto:andrea.a...@geo-solutions.it wrote: On Fri, Jan 30, 2015 at 7:29 PM, Jody Garnett jody.garn...@gmail.commailto:jody.garn...@gmail.com wrote: I guess I see where the friction is coming from, you are focused on the external name used by WMS and I am thinking of keeping our internal catalog consistent. Usually we have kept the name as internal machine readable for machine to machine communication, keeping the title and description for humans. Let me
[Geoserver-devel] [jira] (GEOS-6867) Filter validation fails in WFS when a join needs to be reordered, and has local, non joining filters
Title: Message Title Andrea Aime created an issue GeoServer / GEOS-6867 Filter validation fails in WFS when a join needs to be reordered, and has local, non joining filters Issue Type: Bug Affects Versions: 2.6.2 Assignee: Andrea Aime Components: WFS Created: 02/Feb/15 11:29 AM Priority: Major Reporter: Andrea Aime This happens when the local non joining filters use attributes whose name is not shared among the various feature types, because the feature types the validation is using as target are out of order when the join needed to be reodered to generate a star join that geotools can handle Add Comment
[Geoserver-devel] WFS 2.0.0 and GML 3.1.1
Is there a known issue with combining WFS 2.0.0 and GML 3.1.1? As far as I
can tell, there isn't any reason this would be an unsupported combination.
Testing on all currently available versions of GeoServer (2.5.4, 2.6.2, and
2.7beta) yield the same exception:
ows:ExceptionReport xmlns:ows=http://www.opengis.net/ows/1.1; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance; version=2.0.0
xsi:schemaLocation=http://www.opengis.net/ows/1.1
http://localhost:8080/geoserver/schemas/ows/1.1.0/owsAll.xsd;
ows:Exception exceptionCode=NoApplicableCode
ows:ExceptionText
java.lang.RuntimeException: Failed to get property: {
http://www.opengis.net/gml}featureMembers Failed to get property: {
http://www.opengis.net/gml}featureMembers
net.opengis.wfs20.impl.FeatureCollectionTypeImpl cannot be cast to
net.opengis.wfs.FeatureCollectionType
/ows:ExceptionText
/ows:Exception
/ows:ExceptionReport
For reference I was making a GetFeature request with the following query:
http://localhost:8080/geoserver/topp/ows?service=WFSversion=2.0.0request=GetFeaturetypeName=topp:tasmania_citiescount=50outputFormat=text/xml;%20subtype=gml/3.1.1
I also tried the query against WFS and global OWS service, as opposed to
the virtual topp OWS.
v/r,
Jonathan Meyer
Applied Information Sciences
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Build failed in Jenkins: geoserver-2.6.x #94
See http://ares.opengeo.org/jenkins/job/geoserver-2.6.x/94/changes Changes: [andrea.aime] [GEOS-6867] Filter validation fails in WFS when a join needs to be reordered, and has local, non joining filters -- [...truncated 21096 lines...] [INFO] Application Schema Integration Test ... SKIPPED [INFO] Sample DataAccess Integration Test SUCCESS [39.777s] [INFO] ArcSDE DataStore Extension SUCCESS [32.484s] [INFO] GeoSearch Index Module SKIPPED [INFO] H2 DataStore Extension SUCCESS [20.765s] [INFO] SQL Server DataStore Extension SUCCESS [1.091s] [INFO] Oracle DataStore Extension SUCCESS [2.809s] [INFO] MySQL DataStore Extension . SUCCESS [0.408s] [INFO] DB2 DataStore Extension ... SUCCESS [0.411s] [INFO] ImageMap Output Format SKIPPED [INFO] ImageI/O-Ext GDAL Coverage Extension .. SUCCESS [0.981s] [INFO] JP2K Coverage Extension ... SUCCESS [0.503s] [INFO] ogr2ogr Output Format . SUCCESS [35.902s] [INFO] Excel Output Format ... SUCCESS [36.331s] [INFO] Chart external graphics support ... SUCCESS [1.039s] [INFO] Feature Generalization Extension .. SUCCESS [4.895s] [INFO] Image Mosaic JDBC Extension ... SUCCESS [1.156s] [INFO] OWS request flow controller ... SUCCESS [28.828s] [INFO] Web Processing Service parent . SUCCESS [0.295s] [INFO] Web Processing Service Module . SKIPPED [INFO] Web Processing Service GUI SKIPPED [INFO] GeoServer Layer Querying filter functions . SUCCESS [51.772s] [INFO] Teradata DataStore Extension .. SUCCESS [4.151s] [INFO] GeoServer Monitor Extensions .. SUCCESS [0.205s] [INFO] Core Monitor Extension SKIPPED [INFO] Monitor Hibernate Extension ... SKIPPED [INFO] GeoServer Security Extension Modules .. SKIPPED [INFO] GeoServer CAS Security Module . SKIPPED [INFO] GeoServer Security Extension Web Modules .. SKIPPED [INFO] GeoServer CAS Security Web Module . SKIPPED [INFO] XLST based WFS output format .. SKIPPED [INFO] GeoServer INSPIRE Extensions .. SKIPPED [INFO] GeoServer CSS Styling . SUCCESS [53.413s] [INFO] Catalog Services for the Web parent ... SUCCESS [0.342s] [INFO] Catalog Services for the Web interfaces ... SUCCESS [27.555s] [INFO] Catalog Services for the Web - Simple CatalogStore implementation SUCCESS [27.360s] [INFO] Catalog Services for the Web core module .. SKIPPED [INFO] CSW UI Module . SKIPPED [INFO] DXF WFS output format and WPS PPIO SUCCESS [0.281s] [INFO] DXF WFS output format . SUCCESS [38.731s] [INFO] DXF WPS PPIO .. SKIPPED [INFO] GeoServer WCS 2.0 Earth Observation Extensions SUCCESS [0.276s] [INFO] Web Coverage Service 2.0 Earth Observation extensions SUCCESS [1:05.145s] [INFO] Web Coverage Service 2.0 Earth Observation GUI extension SKIPPED [INFO] GeoServer libjpeg-turbo Module SKIPPED [INFO] GeoServer Data Importer ... SKIPPED [INFO] Importer Core Module .. SKIPPED [INFO] Importer REST Api Module .. SKIPPED [INFO] Importer Berkley DB Persistence Module SKIPPED [INFO] Importer Web UI Module SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 22:45.708s (Wall Clock) [INFO] Finished at: Mon Feb 02 19:14:01 UTC 2015 [INFO] Final Memory: 61M/196M [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.128 sec Running org.geoserver.wps.gs.UniqueProcessTest [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project gs-gwc: Compilation failure: Compilation failure: [ERROR] http://ares.opengeo.org/jenkins/job/geoserver-2.6.x/ws/src/gwc/src/main/java/org/geoserver/gwc/GWC.java:[83,32] error: package org.geowebcache.diskquota does not exist [ERROR] http://ares.opengeo.org/jenkins/job/geoserver-2.6.x/ws/src/gwc/src/main/java/org/geoserver/gwc/GWC.java:[84,32] error: package org.geowebcache.diskquota does not exist [ERROR]
Re: [Geoserver-devel] GWC and workspace specific styles
I was looking at the same two problems in a different way. I'd considered the prefix route on styles but hadn't noticed that solution to the LayerGroups issue and wanted to solve both. So I ended up working on improving the workspace parameter filter option instead, which lead to some improvements in GWC I'm still working on, specifically GWC ticket #170. The work I did should still be able to simplify the Style filter and make it more robust, while also making other new parameter filters with similarly dynamic behaviour easier to write and generally helping to avoid 'leaking' of parameterized tile caches, particular when using the RexExp filter. I don't think my route would have been backportable, and would have been a stretch to make it into GWC 1.7.x/GS 2.7.x now that we are beta so, even though it sort of obsoletes what I've been working on for the past few days, I'm glad to see this. On 1 February 2015 at 03:22, Andrea Aime andrea.a...@geo-solutions.it wrote: On Sun, Feb 1, 2015 at 11:47 AM, Andrea Aime andrea.a...@geo-solutions.it wrote: Going to have a look also at http://jira.codehaus.org/browse/GEOS-6512, it was reported against the opengeo suite (sigh!), but I guess it can be reproduced also with a standard geoserver. Turns out this one was quicker to fix. I did not push because it depends on pull 908, but you can review the changes here, it was a simple logic mistake in the WMS workspace qualifier: https://github.com/aaime/geoserver/commit/c88de8f3d085fad228878561dc9f7a57467a32b5 Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy 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. --- -- Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel -- Kevin Smith Software Engineer | Boundless http://boundlessgeo.com/ ksm...@boundlessgeo.com +1-778-785-7459 @boundlessgeo http://twitter.com/boundlessgeo/ http://twitter.com/boundlessgeo/ [image: http://boundlessgeo.com/] http://boundlessgeo.com/ -- Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the
