[TinyOWS-users] TinyOWS vs. deegree vs. Geoserver andGetFeature GET/POST URLs

[Olivier Courtin]

On May 12, 2011, at 9:42 PM, Rahkonen Jukka wrote:

Jukka,


> Just that TinyOWS sends two separate ows:DCPs for Get and Post like  
> here:

Ok get it  !    Thanks for the explanation :)


I inspect it a bit deeper, and if i remove a DCP element to store both  
Get and Post together
(as Deegree or GeoServer do),

Well, it brakes the WFS Schema GetCapabilities output. (and also  
logically broke several CITE units tests)

I just don't really understand now, how they could be both wrong on  
this point.


> I somehow feel that the parser in deegree client stops parsing when  
> it finds the first ending </ows:DCP but I have not gotten an answer  
> from deegree list yet.

Yeap i'm interrested by theyr answers too !


--
Olivier