[Geoserver-devel] Build failed in Hudson: cite-wms-1.3-trunk #290
See http://hudson.opengeo.org/hudson/job/cite-wms-1.3-trunk/290/ -- [...truncated 1580 lines...] Test getmap:two-styles Passed Testing getmap:three-styles (wms-1.3.0/d39e16863_1/d39e3979_1/d39e4220_1)... Assertion: When a GetMap request contains three valid layers and three valid styles (separated by commas), then the response is valid. Test getmap:three-styles Passed Testing getmap:invalid-style (wms-1.3.0/d39e16863_1/d39e3979_1/d39e4222_1)... Assertion: When a GetMap request contains an unadvertised Style, then the response is an exception (code=StyleNotDefined). Test getmap:invalid-style Passed Testing getmap:styles-default-single-layer (wms-1.3.0/d39e16863_1/d39e3979_1/d39e4225_1)... Assertion: When a GetMap request contains a single layer and a null style value (as in STYLES=), then the response is valid. Test getmap:styles-default-single-layer Passed Testing getmap:styles-default-multiple-layers (wms-1.3.0/d39e16863_1/d39e3979_1/d39e4227_1)... Assertion: When a GetMap request contains multiple layers and requests all layers to be shown in the default style by using a single null value (as in STYLES=), then the response is valid. Test getmap:styles-default-multiple-layers Passed Testing getmap:styles-default-commas (wms-1.3.0/d39e16863_1/d39e3979_1/d39e4229_1)... Assertion: When a GetMap request contains multiple layers and requests all layers to be shown in the default style by using null values between commas (as in STYLES=,,,), then the response is valid. Test getmap:styles-default-commas Passed Testing getmap:styles-some-default (wms-1.3.0/d39e16863_1/d39e3979_1/d39e4231_1)... Assertion: When a GetMap request contains multiple layers and a mixture of named and default styles (as in STYLES=style1,,style2,,), then the response is valid. Test getmap:styles-some-default Passed Testing getmap:first-style-invalid (wms-1.3.0/d39e16863_1/d39e3979_1/d39e4233_1)... Assertion: When a GetMap request contains two layers, where the first style is not valid and the second style is, then the response is an exception (code=StyleNotDefined). Test getmap:first-style-invalid Passed Testing getmap:second-style-invalid (wms-1.3.0/d39e16863_1/d39e3979_1/d39e4235_1)... Assertion: When a GetMap request contains two layers, where the first style is valid and the second style is not, then the response is an exception (code=StyleNotDefined). Test getmap:second-style-invalid Passed Testing getmap:each-style (wms-1.3.0/d39e16863_1/d39e3979_1/d39e4242_1)... Assertion: For style point, when the STYLES parameter is set to that style name, the MIME type of the response is valid. Test getmap:each-style Passed Testing getmap:each-style (wms-1.3.0/d39e16863_1/d39e3979_1/d39e4242_2)... Assertion: For style BasicPolygons, when the STYLES parameter is set to that style name, the MIME type of the response is valid. Test getmap:each-style Passed Testing getmap:each-style (wms-1.3.0/d39e16863_1/d39e3979_1/d39e4242_3)... Assertion: For style Bridges, when the STYLES parameter is set to that style name, the MIME type of the response is valid. Test getmap:each-style Passed Testing getmap:each-style (wms-1.3.0/d39e16863_1/d39e3979_1/d39e4242_4)... Assertion: For style Buildings, when the STYLES parameter is set to that style name, the MIME type of the response is valid. Test getmap:each-style Passed Testing getmap:each-style (wms-1.3.0/d39e16863_1/d39e3979_1/d39e4242_5)... Assertion: For style DividedRoutes, when the STYLES parameter is set to that style name, the MIME type of the response is valid. Test getmap:each-style Passed Testing getmap:each-style (wms-1.3.0/d39e16863_1/d39e3979_1/d39e4242_6)... Assertion: For style Forests, when the STYLES parameter is set to that style name, the MIME type of the response is valid. Test getmap:each-style Passed Testing getmap:each-style (wms-1.3.0/d39e16863_1/d39e3979_1/d39e4242_7)... Assertion: For style Lakes, when the STYLES parameter is set to that style name, the MIME type of the response is valid. Test getmap:each-style Passed Testing getmap:each-style (wms-1.3.0/d39e16863_1/d39e3979_1/d39e4242_8)... Assertion: For style polygon, when the STYLES parameter is set to that style name, the MIME type of the response is valid. Test getmap:each-style Passed Testing getmap:each-style
[Geoserver-devel] Build failed in Hudson: cite-wfs-1.1-trunk #414
See http://hudson.opengeo.org/hudson/job/cite-wfs-1.1-trunk/414/ -- [...truncated 3848 lines...] Testing wfs:GetFeatureById-KVP (wfs-1.1.0/d39e34902_1/d39e743_1/d39e31854_1/d39e26592_1/d39e29266_1)... Assertion: Attempts to fetch a feature by identifier using the GetFeature/GET binding. Validation warning: SchemaLocation: schemaLocation value = ' http://localhost:11010/geoserver/wfs?service=WFSversion=1.1.0request=DescribeFeatureTypetypeName=sf%3APrimitiveGeoFeature http://www.opengis.net/wfs http://localhost:11010/geoserver/schemas/wfs/1.1.0/wfs.xsd' must have even number of URI's. 1 warning detected. Test wfs:GetFeatureById-KVP Passed Testing wfs:GetFeatureById-KVP (wfs-1.1.0/d39e34902_1/d39e743_1/d39e31854_1/d39e26592_1/d39e29276_1)... Assertion: Attempts to fetch a feature by identifier using the GetFeature/GET binding. Validation warning: SchemaLocation: schemaLocation value = ' http://localhost:11010/geoserver/wfs?service=WFSversion=1.1.0request=DescribeFeatureTypetypeName=sf%3APrimitiveGeoFeature http://www.opengis.net/wfs http://localhost:11010/geoserver/schemas/wfs/1.1.0/wfs.xsd' must have even number of URI's. 1 warning detected. Test wfs:GetFeatureById-KVP Passed Testing wfs:GetFeatureById-KVP (wfs-1.1.0/d39e34902_1/d39e743_1/d39e31854_1/d39e26592_1/d39e29285_1)... Assertion: Attempts to fetch a feature by identifier using the GetFeature/GET binding. Validation warning: SchemaLocation: schemaLocation value = ' http://localhost:11010/geoserver/wfs?service=WFSversion=1.1.0request=DescribeFeatureTypetypeName=sf%3AEntit%E9G%E9n%E9rique http://www.opengis.net/wfs http://localhost:11010/geoserver/schemas/wfs/1.1.0/wfs.xsd' must have even number of URI's. 1 warning detected. Test wfs:GetFeatureById-KVP Passed Test wfs:wfs-1.1.0-Transaction-tc13.1 Passed Testing wfs:run-Transaction-Cleanup (wfs-1.1.0/d39e34902_1/d39e743_1/d39e31854_1/d39e26617_1)... Assertion: Run test group for cleaning up (deleting) the features inserted by the Transactions. Testing wfs:delete-test-data (wfs-1.1.0/d39e34902_1/d39e743_1/d39e31854_1/d39e26617_1/d39e25265_1)... Assertion: Deletes the test data used in transactions during the test run. Testing wfs:delete-feature (wfs-1.1.0/d39e34902_1/d39e743_1/d39e31854_1/d39e26617_1/d39e25265_1/d39e25292_1)... Assertion: Deletes a feature by typename and gml:name. Test wfs:delete-feature Passed Testing wfs:delete-feature (wfs-1.1.0/d39e34902_1/d39e743_1/d39e31854_1/d39e26617_1/d39e25265_1/d39e25301_1)... Assertion: Deletes a feature by typename and gml:name. Test wfs:delete-feature Passed Testing wfs:delete-feature (wfs-1.1.0/d39e34902_1/d39e743_1/d39e31854_1/d39e26617_1/d39e25265_1/d39e25310_1)... Assertion: Deletes a feature by typename and gml:name. Test wfs:delete-feature Passed Testing wfs:delete-feature (wfs-1.1.0/d39e34902_1/d39e743_1/d39e31854_1/d39e26617_1/d39e25265_1/d39e25319_1)... Assertion: Deletes a feature by typename and gml:name. Test wfs:delete-feature Passed Testing wfs:delete-feature (wfs-1.1.0/d39e34902_1/d39e743_1/d39e31854_1/d39e26617_1/d39e25265_1/d39e25328_1)... Assertion: Deletes a feature by typename and gml:name. Test wfs:delete-feature Passed Testing wfs:delete-feature (wfs-1.1.0/d39e34902_1/d39e743_1/d39e31854_1/d39e26617_1/d39e25265_1/d39e25338_1)... Assertion: Deletes a feature by typename and gml:name. Test wfs:delete-feature Passed Testing wfs:delete-feature (wfs-1.1.0/d39e34902_1/d39e743_1/d39e31854_1/d39e26617_1/d39e25265_1/d39e25347_1)... Assertion: Deletes a feature by typename and gml:name. Test wfs:delete-feature Passed Testing wfs:delete-feature (wfs-1.1.0/d39e34902_1/d39e743_1/d39e31854_1/d39e26617_1/d39e25265_1/d39e25356_1)... Assertion: Deletes a feature by typename and gml:name. Test wfs:delete-feature Passed Testing wfs:delete-feature (wfs-1.1.0/d39e34902_1/d39e743_1/d39e31854_1/d39e26617_1/d39e25265_1/d39e25365_1)... Assertion: Deletes a feature by typename and gml:name. Test wfs:delete-feature Passed
[Geoserver-devel] Projections problem
Hello, I have some orthophotos that have projection: Transverse Mercator, Datum: WGS84, Planar Units: Meters ... I convert in projection: Geographic (Latitude, Longitude), Datum: WGS84, Planar Units: ARC DEGREES. When I upload this photos with new projections in GeoServer and I insert some pictures in group of layers I see that I have some white lines between pictures, have can I find the solution for this problem, with white lines between pictures ? -- Regards Besfort Guri +377 44 49 88 91 www.besiguri.wordpress.com http://besfortp.posterous.com/ -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [jira] Created: (GEOS-4777) Allow layers to be available, but not advertised in the capabilities documents
Allow layers to be available, but not advertised in the capabilities documents -- Key: GEOS-4777 URL: https://jira.codehaus.org/browse/GEOS-4777 Project: GeoServer Issue Type: New Feature Components: Configuration, WCS, WFS, WMS Affects Versions: 2.1.1 Reporter: Andrea Aime Assignee: Andrea Aime Fix For: 2.1.2 See discussion on the mailing list: http://osgeo-org.1803224.n2.nabble.com/New-feature-hiding-layers-from-capabilities-td6762948.html http://osgeo-org.1803224.n2.nabble.com/Non-advertised-layers-a-bit-of-design-discussion-td6839167.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [jira] Created: (GEOS-4778) Virtual services do not play well with layer groups
Virtual services do not play well with layer groups --- Key: GEOS-4778 URL: https://jira.codehaus.org/browse/GEOS-4778 Project: GeoServer Issue Type: Bug Components: Global Affects Versions: 2.1.1 Reporter: Andrea Aime Assignee: Andrea Aime Fix For: 2.1.2 A request like: http://localhost:8080/geoserver/sf/wms?service=WMSversion=1.1.0request=GetMaplayers=spearfishstyles=bbox=589425.9342365642,4913959.224611808,609518.6719560538,4928082.949945881width=512height=359srs=EPSG:26713format=application/openlayers does not work because the layer group name gets qualified by WMSWorkspaceQualifier from spearfish into sf:spearfish. The qualifier should not touch the layer group name. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [jira] Created: (GEOS-4779) Log location system variable override ignored when the logs are reconfigured at runtime
Log location system variable override ignored when the logs are reconfigured at runtime --- Key: GEOS-4779 URL: https://jira.codehaus.org/browse/GEOS-4779 Project: GeoServer Issue Type: Bug Components: Configuration Affects Versions: 2.1.1 Reporter: Andrea Aime Assignee: Andrea Aime Fix For: 2.1.2 The log location does not work anymore if the server panel is used to reconfigure the log properties at runtime -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Build failed in Hudson: geoserver-2.1.x #432
See http://hudson.opengeo.org/hudson/job/geoserver-2.1.x/432/changes
Changes:
[aaime] [GEOS-4777] Allow layers to be available, but not advertised in the
capabilities documents
--
[...truncated 661 lines...]
[INFO] snapshot org.geotools:extension:2.7-SNAPSHOT: checking for updates from
opengeo
[INFO] snapshot org.geotools:extension:2.7-SNAPSHOT: checking for updates from
osgeo
[INFO] snapshot org.geotools.xsd:gt-xsd-filter:2.7-SNAPSHOT: checking for
updates from opengeo
[INFO] snapshot org.geotools.xsd:gt-xsd-filter:2.7-SNAPSHOT: checking for
updates from osgeo
[INFO] snapshot org.geotools.xsd:gt-xsd-filter:2.7-SNAPSHOT: checking for
updates from maven2-repository.dev.java.net
[INFO] snapshot org.geotools:gt-coverage:2.7-SNAPSHOT: checking for updates
from opengeo
[INFO] snapshot org.geotools:gt-coverage:2.7-SNAPSHOT: checking for updates
from osgeo
[INFO] snapshot org.geotools:gt-coverage:2.7-SNAPSHOT: checking for updates
from maven2-repository.dev.java.net
[INFO] snapshot org.geotools.xsd:gt-xsd-core:2.7-SNAPSHOT: checking for updates
from opengeo
[INFO] snapshot org.geotools.xsd:gt-xsd-core:2.7-SNAPSHOT: checking for updates
from osgeo
[INFO] snapshot org.geotools.xsd:gt-xsd-core:2.7-SNAPSHOT: checking for updates
from maven2-repository.dev.java.net
[INFO] snapshot org.geotools:gt-graph:2.7-SNAPSHOT: checking for updates from
opengeo
[INFO] snapshot org.geotools:gt-graph:2.7-SNAPSHOT: checking for updates from
osgeo
[INFO] snapshot org.geotools:gt-graph:2.7-SNAPSHOT: checking for updates from
maven2-repository.dev.java.net
[INFO] snapshot org.geotools.xsd:gt-xsd-gml2:2.7-SNAPSHOT: checking for updates
from opengeo
[INFO] snapshot org.geotools.xsd:gt-xsd-gml2:2.7-SNAPSHOT: checking for updates
from osgeo
[INFO] snapshot org.geotools.xsd:gt-xsd-gml2:2.7-SNAPSHOT: checking for updates
from maven2-repository.dev.java.net
[INFO] snapshot org.geotools.xsd:gt-xsd-gml3:2.7-SNAPSHOT: checking for updates
from opengeo
[INFO] snapshot org.geotools.xsd:gt-xsd-gml3:2.7-SNAPSHOT: checking for updates
from osgeo
[INFO] snapshot org.geotools.xsd:gt-xsd-gml3:2.7-SNAPSHOT: checking for updates
from maven2-repository.dev.java.net
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 82 source files to
http://hudson.opengeo.org/hudson/job/geoserver-2.1.x/ws/geoserver-2.1.x/ows/target/classes
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 4 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 18 source files to
http://hudson.opengeo.org/hudson/job/geoserver-2.1.x/ws/geoserver-2.1.x/ows/target/test-classes
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory:
http://hudson.opengeo.org/hudson/job/geoserver-2.1.x/ws/geoserver-2.1.x/ows/target/surefire-reports
---
T E S T S
---
Running org.geoserver.ows.util.OwsUtilsTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.04 sec
Running org.geoserver.ows.DispatcherTest
Sep 29, 2011 1:27:05 PM org.geoserver.platform.GeoServerExtensions checkContext
SEVERE: Extension lookup occured, but ApplicationContext is unset.
Sep 29, 2011 1:27:05 PM org.geoserver.platform.GeoServerExtensions checkContext
SEVERE: Extension lookup occured, but ApplicationContext is unset.
Sep 29, 2011 1:27:05 PM org.geoserver.platform.GeoServerExtensions checkContext
SEVERE: Extension lookup occured, but ApplicationContext is unset.
Sep 29, 2011 1:27:05 PM org.geoserver.platform.GeoServerExtensions checkContext
SEVERE: Extension lookup occured, but ApplicationContext is unset.
Sep 29, 2011 1:27:05 PM
org.springframework.context.support.AbstractApplicationContext prepareRefresh
INFO: Refreshing
org.springframework.context.support.FileSystemXmlApplicationContext@e6ff0d:
display name
[org.springframework.context.support.FileSystemXmlApplicationContext@e6ff0d];
startup date [Thu Sep 29 13:27:05 UTC 2011]; root of context hierarchy
Sep 29, 2011 1:27:05 PM
org.springframework.beans.factory.xml.XmlBeanDefinitionReader
loadBeanDefinitions
INFO: Loading XML bean definitions from URL
[http://hudson.opengeo.org/hudson/job/geoserver-2.1.x/ws/geoserver-2.1.x/ows/target/test-classes/org/geoserver/ows/applicationContext.xml]
Sep 29, 2011 1:27:05 PM
org.springframework.context.support.AbstractApplicationContext
obtainFreshBeanFactory
INFO: Bean factory for application context
[org.springframework.context.support.FileSystemXmlApplicationContext@e6ff0d]:
org.springframework.beans.factory.support.DefaultListableBeanFactory@b33d0a
Sep 29, 2011 1:27:05 PM
org.springframework.beans.factory.support.DefaultListableBeanFactory
preInstantiateSingletons
INFO: Pre-instantiating singletons in
[Geoserver-devel] Hudson build is back to normal : geoserver-2.1.x #433
See http://hudson.opengeo.org/hudson/job/geoserver-2.1.x/433/changes -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GSIP 64 - Keyword Vocabularies and Languages
Thanks for the prompt feedback Andrea. Comments inline. On Thu, Sep 29, 2011 at 8:08 AM, Andrea Aime andrea.a...@geo-solutions.itwrote: On Thu, Sep 29, 2011 at 5:38 AM, Justin Deoliveira jdeol...@opengeo.orgwrote: Hi all, I have put together a quick proposal and patch to allow for supporting specifying metadata on service and layer keywords. The current proposal is here: http://geoserver.org/display/GEOS/GSIP+64+-+Keyword+Vocabularies+and+Languages Current patch on github: https://github.com/jdeolive/geoserver/commit/256f9037924bf6866495e2f72b3072cd443df0cf Related JIRA issue: http://jira.codehaus.org/browse/GEOS-4658 Feedback appreciated. The proposal makes sense and seems rather complete. The backwards compatibility strategy is also good, though I don't see escaping for the separators: are they invalid characters in the keyword, language or vocabulary expressions? Ahh good point. As far as WMS and OWS go they can be arbitrary strings to @ and ; are valid. Will escape them. Besides this issue, +1 Thinking out loud, expression a keyword becomes more work, might be interesting to have a way to copy them from another layer. I think others have expressed a desire to have existing layers act as templates for new layers. Anyways, just a random thought, not actually related to the proposal Yeah that is a cool idea... template layers like we have template styles... would be a fun one to implement :) Cheers Andrea -- --- Ing. Andrea Aime GeoSolutions S.A.S. Tech lead Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 962313 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.youtube.com/user/GeoSolutionsIT http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf --- -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [jira] Created: (GEOS-4780) Cascaded WMS Layers not available from rest/layers/layername.xml endpoint
Cascaded WMS Layers not available from rest/layers/layername.xml endpoint --- Key: GEOS-4780 URL: https://jira.codehaus.org/browse/GEOS-4780 Project: GeoServer Issue Type: Bug Components: REST Reporter: Jeffrey Johnson Assignee: Andrea Aime Priority: Minor While Cascaded layers are advertised as being available at http://localhost:8080/geoserver/rest/layers.xml .. the URL provided for a cascaded wms layer in an individual layer block in that output returns 404 with No such layer: layer_name -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GSIP 64 - Keyword Vocabularies and Languages
Hey Justin! The proposal looks good; +1 Q: do you have a real example of what vocabulary can be? Q: Did you consider integration with InternationalString? -- Jody Garnett On Thursday, 29 September 2011 at 1:38 PM, Justin Deoliveira wrote: Hi all, I have put together a quick proposal and patch to allow for supporting specifying metadata on service and layer keywords. The current proposal is here: http://geoserver.org/display/GEOS/GSIP+64+-+Keyword+Vocabularies+and+Languages Current patch on github: https://github.com/jdeolive/geoserver/commit/256f9037924bf6866495e2f72b3072cd443df0cf Related JIRA issue: http://jira.codehaus.org/browse/GEOS-4658 Feedback appreciated. Thanks. -Justin -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net (mailto:Geoserver-devel@lists.sourceforge.net) https://lists.sourceforge.net/lists/listinfo/geoserver-devel -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
