I've run into some failures running the cite tests for the 2.0.1 release. The first batch are the wfs 1.0.0 tests. I seem to recall some issues with these tests using the newer cite engine due to the engines inability to resolve some namespaces, but these failures occur on both versions of the engine that I've used. I've had a look at the logs, but I'm not seeing some of the nice error messages I've come to expect. If someone in the know could have a look and tell me what they think, I'd appreciate this. There will be some 1.1.0 issues following shortly 
--
Mark
(attachments)
wfs-1.0.0-failures.zip (9.08 KB)
Hmmmm... this form of the logs can be hard to follow, and don't really contain the most relevant info. Is there any chance you make the contents of the cite/target/work directory available? That way somone can start up the teamengine locally and navigate the logs via the teamengine webapp.
I am of course assuming that you are following this guide to run the tests:
http://docs.geoserver.org/2.0.x/en/developer/cite-test-guide/index.html#cite-test-guide
-Justin
Mark Leslie wrote:
I've run into some failures running the cite tests for the 2.0.1 release. The first batch are the wfs 1.0.0 tests. I seem to recall some issues with these tests using the newer cite engine due to the engines inability to resolve some namespaces, but these failures occur on both versions of the engine that I've used. I've had a look at the logs, but I'm not seeing some of the nice error messages I've come to expect. If someone in the know could have a look and tell me what they think, I'd appreciate this. There will be some 1.1.0 issues following shortly
--
Mark
------------------------------------------------------------------------
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Those are the instructions I'm using. Here's a copy fo my work directory.
________________________________________
From: Justin Deoliveira [jdeolive@anonymised.com]
Sent: Wednesday, 23 December 2009 1:56 PM
To: Mark Leslie
Cc: geoserver-devel@lists.sourceforge.net
Subject: Re: [Geoserver-devel] Cite tests for 2.0.1 release: wfs-1.0.0
Hmmmm... this form of the logs can be hard to follow, and don't really
contain the most relevant info. Is there any chance you make the
contents of the cite/target/work directory available? That way somone
can start up the teamengine locally and navigate the logs via the
teamengine webapp.
I am of course assuming that you are following this guide to run the tests:
http://docs.geoserver.org/2.0.x/en/developer/cite-test-guide/index.html#cite-test-guide
-Justin
Mark Leslie wrote:
I've run into some failures running the cite tests for the 2.0.1 release. The first batch are the wfs 1.0.0 tests. I seem to recall some issues with these tests using the newer cite engine due to the engines inability to resolve some namespaces, but these failures occur on both versions of the engine that I've used. I've had a look at the logs, but I'm not seeing some of the nice error messages I've come to expect. If someone in the know could have a look and tell me what they think, I'd appreciate this. There will be some 1.1.0 issues following shortly
--
Mark
------------------------------------------------------------------------
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
(attachments)
cite-work.zip (1.34 MB)
Finally got around to looking into this and indeed there are some legit failures due to some recent dft changes.
The patch is simple, will commit it on 2.0.x and trunk shortly. And I guess port it to the 2.0.1 tag as well.
-Justin
Mark Leslie wrote:
Those are the instructions I'm using. Here's a copy fo my work directory.
________________________________________
From: Justin Deoliveira [jdeolive@anonymised.com]
Sent: Wednesday, 23 December 2009 1:56 PM
To: Mark Leslie
Cc: geoserver-devel@lists.sourceforge.net
Subject: Re: [Geoserver-devel] Cite tests for 2.0.1 release: wfs-1.0.0
Hmmmm... this form of the logs can be hard to follow, and don't really
contain the most relevant info. Is there any chance you make the
contents of the cite/target/work directory available? That way somone
can start up the teamengine locally and navigate the logs via the
teamengine webapp.
I am of course assuming that you are following this guide to run the tests:
http://docs.geoserver.org/2.0.x/en/developer/cite-test-guide/index.html#cite-test-guide
-Justin
Mark Leslie wrote:
I've run into some failures running the cite tests for the 2.0.1 release. The first batch are the wfs 1.0.0 tests. I seem to recall some issues with these tests using the newer cite engine due to the engines inability to resolve some namespaces, but these failures occur on both versions of the engine that I've used. I've had a look at the logs, but I'm not seeing some of the nice error messages I've come to expect. If someone in the know could have a look and tell me what they think, I'd appreciate this. There will be some 1.1.0 issues following shortly
--
Mark
------------------------------------------------------------------------
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Excellent, thanks Justin. I'll grab the changes and try again.
--
Mark
Justin Deoliveira wrote:
Finally got around to looking into this and indeed there are some legit failures due to some recent dft changes.
The patch is simple, will commit it on 2.0.x and trunk shortly. And I guess port it to the 2.0.1 tag as well.
-Justin
Mark Leslie wrote:
Those are the instructions I'm using. Here's a copy fo my work directory.
________________________________________
From: Justin Deoliveira [jdeolive@anonymised.com]
Sent: Wednesday, 23 December 2009 1:56 PM
To: Mark Leslie
Cc: geoserver-devel@lists.sourceforge.net
Subject: Re: [Geoserver-devel] Cite tests for 2.0.1 release: wfs-1.0.0
Hmmmm... this form of the logs can be hard to follow, and don't really
contain the most relevant info. Is there any chance you make the
contents of the cite/target/work directory available? That way somone
can start up the teamengine locally and navigate the logs via the
teamengine webapp.
I am of course assuming that you are following this guide to run the tests:
http://docs.geoserver.org/2.0.x/en/developer/cite-test-guide/index.html#cite-test-guide
-Justin
Mark Leslie wrote:
I've run into some failures running the cite tests for the 2.0.1 release. The first batch are the wfs 1.0.0 tests. I seem to recall some issues with these tests using the newer cite engine due to the engines inability to resolve some namespaces, but these failures occur on both versions of the engine that I've used. I've had a look at the logs, but I'm not seeing some of the nice error messages I've come to expect. If someone in the know could have a look and tell me what they think, I'd appreciate this. There will be some 1.1.0 issues following shortly
--
Mark
------------------------------------------------------------------------
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel