Thanks Andrea, that seems to have done the trick.
-Lucas
Andrea Aime wrote:
> Andrea Aime ha scritto:
> ...
>> Sure thing, works for me:
>> http://jira.codehaus.org/browse/GEOS-1967
>> (working on it)
>
> Ok, if you look in OWS, you'll find a CodeTypeParser
> that the wcs 1.1 code extends. I als
Andrea Aime ha scritto:
...
> Sure thing, works for me:
> http://jira.codehaus.org/browse/GEOS-1967
> (working on it)
Ok, if you look in OWS, you'll find a CodeTypeParser
that the wcs 1.1 code extends. I also made it specify
the service name, so it should not clash anymore with
wps. Lucas, have a
Justin Deoliveira ha scritto:
> Hi Lucas,
>
> I looked into it and I see the issue. The simple solution is attach
> service=WCS to the wcs kvp parser so it does not conflict. However...
> both the kvp readers return a CodeType instance from the ows model... so
> it would be duplication. Howev
Hi Lucas,
I looked into it and I see the issue. The simple solution is attach
service=WCS to the wcs kvp parser so it does not conflict. However...
both the kvp readers return a CodeType instance from the ows model... so
it would be duplication. However... the wcs parser uses the identifier
Hi,
I've run into a problem parsing a KVP DescribeProcess request with
the WPS module.
Both WCS and WPS have custom KVP parsers for the 'Identifier' key.
WCS' parser does not seem to have its service string set when the
KvpUtils.parse() method prunes the list of possible parsers.
Since they bot
