Hi Andrea,
While running wfs 1.1 cite tests i have been running into conflicts
between the normal wfs xml reader and the versioned one. Basically both
of them latch onto the "wfs:Transaction" element and at the moment the
versioned one is winning out. This is causing the xml configuration
(some of the binding overrides) not to engage.
It should not be hard to fix... i just need to understand when the
versioning xml reader should engage. Should it always engage if the wfsv
plugin is active? Or is there something that can be checked in the
request that specifies that the request is a versioned one?
-Justin
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
Justin Deoliveira ha scritto:
Hi Andrea,
While running wfs 1.1 cite tests i have been running into conflicts
between the normal wfs xml reader and the versioned one. Basically both
of them latch onto the "wfs:Transaction" element and at the moment the
versioned one is winning out. This is causing the xml configuration
(some of the binding overrides) not to engage.
It should not be hard to fix... i just need to understand when the
versioning xml reader should engage. Should it always engage if the wfsv
plugin is active? Or is there something that can be checked in the
request that specifies that the request is a versioned one?
The versioning one should engage only if the service used is WFSV, not
when its WFS. Funny, why is that not happening on 1.6.x? (we do pass
the wfs cite tests don't we?).
Cheers
Andrea