Hi,
on trunk we have a citewfs configuration along with the cite
one. Hmm... fact is, it's unusable because it misses catalog and
services.xml.
So, in order to run wfs 1.0 tests I have to use the cite configuration
anyways.
Cheers
Andrea
Hi,
on trunk we have a citewfs configuration along with the cite
one. Hmm... fact is, it's unusable because it misses catalog and
services.xml.
So, in order to run wfs 1.0 tests I have to use the cite configuration
anyways.
Cheers
Andrea
Andrea Aime wrote:
Hi,
on trunk we have a citewfs configuration along with the cite
one. Hmm... fact is, it's unusable because it misses catalog and
services.xml.
This is something that never got finished. On 1.5.x all the cite
configurations were dumped into one single configuration. However I
raised issues with this and stated that for 1.1 we would need a separate
configuration. The configuration for 1.0 was never really created.
Actually looking in my local workspace it looks like i have one that
hasn't been committed. Shall i go ahead and commit?
So, in order to run wfs 1.0 tests I have to use the cite configuration
anyways.Cheers
Andrea-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel!DSPAM:4007,468a52cf210921012714783!
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
Justin Deoliveira ha scritto:
Andrea Aime wrote:
Hi,
on trunk we have a citewfs configuration along with the cite
one. Hmm... fact is, it's unusable because it misses catalog and
services.xml.This is something that never got finished. On 1.5.x all the cite
configurations were dumped into one single configuration. However I
raised issues with this and stated that for 1.1 we would need a separate
configuration. The configuration for 1.0 was never really created.
Actually looking in my local workspace it looks like i have one that
hasn't been committed. Shall i go ahead and commit?
If you think that's necessary to have wfs 1.0 pass the cite tests
on the new engine yeah, otherwise I would probably remove it...
(since cite configuration covers cite testing needs just fine on
1.5.x)
Cheers
Andrea
Well it was more a consistency thing. Why have a separate module for wfs
1.1 but not for 1.0, or the other services.
Andrea Aime wrote:
Justin Deoliveira ha scritto:
Andrea Aime wrote:
Hi,
on trunk we have a citewfs configuration along with the cite
one. Hmm... fact is, it's unusable because it misses catalog and
services.xml.This is something that never got finished. On 1.5.x all the cite
configurations were dumped into one single configuration. However I
raised issues with this and stated that for 1.1 we would need a separate
configuration. The configuration for 1.0 was never really created.
Actually looking in my local workspace it looks like i have one that
hasn't been committed. Shall i go ahead and commit?If you think that's necessary to have wfs 1.0 pass the cite tests
on the new engine yeah, otherwise I would probably remove it...
(since cite configuration covers cite testing needs just fine on
1.5.x)
Cheers
Andrea!DSPAM:4007,468a6128224631804284693!
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
Justin Deoliveira ha scritto:
Well it was more a consistency thing. Why have a separate module for wfs
1.1 but not for 1.0, or the other services.
Then to be consistent you would have to split out wms and wcs modules too
Cheers
Andrea