Hi Olyster, see comments inline. On Tue, May 14, 2019 at 10:23 PM Olyster <[email protected]> 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 : > > typeName = new QName(ns.getURI(), typeName.getLocalPart()); > You mean WFSWorkspaceQualifier? > As you can see the third parameter (the prefix) is omitted so the resulting > QName doesn't have a prefix (it's equal to an empty string). > > If I replace the calling line with : > > typeName = new QName(ns.getURI(), typeName.getLocalPart(), > typeName.getPrefix()); > > The prefix is kept an the problem is gone. > > My question is : Why is the prefix not passed to the QName constructor ? > Prefixes in XML mean nothing, the namespace it the element that is stable, a prefix can change from request to request. For example, if a xml request uses xmlns:mickeyMouse=" http://www.opengis.net/wfs"; and then prefixes every wfs element with mickeyMouse, e.g. mickeyMouse:GetFeature, then the request is valid. So the norm would be to use the namespace everywhere instead. In GeoServer things are a bit more complicated in that for layers the workspace name is often used as the prefix. Ideally, the code using the QName and assuming the prefix has meaning seems like the one that needs fixing instead of the one not setting it, but I did not check it overall, so it might be more practical to do otherwise. Cheers Andrea == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- *Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.*
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
