[Geoserver-devel] Build failed in Hudson: cite-wms-1.3-trunk #292
See http://hudson.opengeo.org/hudson/job/cite-wms-1.3-trunk/292/ -- [...truncated 1583 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 #416
See http://hudson.opengeo.org/hudson/job/cite-wfs-1.1-trunk/416/ -- [...truncated 3833 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
Re: [Geoserver-devel] GSIP 64 - Keyword Vocabularies and Languages
KeywordList
Keyword vocabulary=ISOinfoMapAccessService/Keyword
Keyword vocabulary=GEMET - INSPIRE themes, version
1.0Hydrography/Keyword
/KeywordList
Okay that works for me; was trying to figure it out looks like one of those
silly domain of discourse ideas.
Q: Did you consider integration with InternationalString?
I had not but that is an interesting thought... I guess we could make
KeywordInfo.value an international string. However it might be overkill
here... i don't really need to convert between languages... just associate a
language with a string. Which InterationalString doesn't really seem to
provide.
Well the thing is a lot of the implementations do provide that; it is just
that InternationalString is a nice way to throw them around a program and
mark down something that has translations. I had a couple goes making
something for keyword but did not like any of them especially.
class KeywordString extends InternationalString {
SetKeyword getKeywords();
String toString();
String toString( Locale );
}
Jody
--
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
Re: [Geoserver-devel] GSIP 64 - Keyword Vocabularies and Languages
Hei Justin, +1 here too ... nice capability to have.
Thanks,
Alessio.
---
Ing. Alessio Fabiani
Founder / CTO GeoSolutions S.A.S.
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: (+39) 0584 96.23.13
fax: (+39) 0584 96.23.13
mobile:(+39) 331 62.33.686
http://www.geo-solutions.it
http://geo-solutions.blogspot.com
http://www.linkedin.com/in/alessiofabiani
http://twitter.com/geosolutions_it
---
On Sat, Oct 1, 2011 at 7:25 AM, Jody Garnett jody.garn...@gmail.com wrote:
KeywordList
Keyword vocabulary=ISOinfoMapAccessService/Keyword
Keyword vocabulary=GEMET - INSPIRE themes, version
1.0Hydrography/Keyword
/KeywordList
Okay that works for me; was trying to figure it out looks like one of those
silly domain of discourse ideas.
Q: Did you consider integration with InternationalString?
I had not but that is an interesting thought... I guess we could make
KeywordInfo.value an international string. However it might be overkill
here... i don't really need to convert between languages... just associate a
language with a string. Which InterationalString doesn't really seem to
provide.
Well the thing is a lot of the implementations do provide that; it is
just that InternationalString is a nice way to throw them around a program
and mark down something that has translations. I had a couple goes making
something for keyword but did not like any of them especially.
class KeywordString extends InternationalString {
SetKeyword getKeywords();
String toString();
String toString( Locale );
}
Jody
--
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
--
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
