virtual services does not play nice with GML 3 encoding

Description

Reason being that the internal XSDSchemas are built from types in a single workspace, but cached globally. So to reproduce make a GML 3.1 request (via a virtual service endpoint) and then make another request that involves a type not that in that workspace (through a virtual service or global)

Environment

None

Status

Assignee

Nuno Oliveira

Reporter

codehaus

Triage

Fix versions

Affects versions

None

Priority

High
Configure