Hi Olyster,
I saw it, but could not put toghether an answer in just a minute so kept on
delaying the answer.
Sorry, I'm overwhelmed with work beyond repair, only the mails that I can
answer super-quickly get answered.
Anyways, I can go for a short and direct response, since I still don't have
Hi,
maybe you didn't get the time to read my reply. I don't want to bug you with
that issue but I just want to make sure if you consider it to be a bug.
If yes, should I make the modification as a quick fix to be released or
create an issue in bug tracker or I should maintain my own version of
Andrea,
thanks for your answer.
You're right, I meant WFSWorkspaceQualifier/qualifyRequest.
I'm working with Hexagon SDI and, only with WFS, as soon as I specify a
workspace or a workspace/layer as a virtual service, Geoserver returns :
Unknown namespace []
Here's an example that's failing
Hi Olyster,
see comments inline.
On Tue, May 14, 2019 at 10:23 PM Olyster wrote:
> Hi,
>
> I'm having a problem using WFS with a virtual service.
>
> After debugging, I found out that the prefix is emptied during the
> GetFeature request.
>
> In WorkspaceQualifier.java, there's this line :
>
>
Hi,
I'm having a problem using WFS with a virtual service.
After debugging, I found out that the prefix is emptied during the
GetFeature request.
In WorkspaceQualifier.java, there's this line :
typeName = new QName(ns.getURI(), typeName.getLocalPart());
As you can see the third parameter
Hi,
There's a problem using WFS with virtual service.
When I use the url http://server/geoserver/workspace/layer/wfs? I get :
exceptionCode="InvalidParameterValue" locator="namespace"
When I use the url http://server/geoserver/wfs? The service works fine.
After debugging, I found out that
