Hi, I don't see how to fix this for the use case where app-schema builds a complex feature using feature chaining. The problem is that in the GML3 encoder we only know the root feature type but there is no way (at least I could not found it) to discovered the chained feature types that were used.
So since we cannot find all the feature types that are used we need to always use all the feature types available in the catalog. Note that WFS 2.0.0 has the same issue, using app-schema feature chaining with WFS 2.0.0 will cause some trouble. So for now, app-schema will still rely on the the full catalog schema. Any other ides on this ? Regards, On 03/06/2017 02:08 PM, Nuno Oliveira wrote: > Hi Ben, > > Thanks for the warning, pull request amended. > > Last minute change and forget to check app-schema tests which proved > that my last minute change was actually a bad idea for when schemas are > provided by the feature type :( > > Kind regards, > > Nuno Oliveira > > On 03/05/2017 08:10 PM, Ben Caradoc-Davies wrote: >> On 06/03/17 06:21, Nuno Oliveira wrote: >>> A pull request for this was made: >>> https://github.com/geoserver/geoserver/pull/2140 >>> Opinions on this ? >> Travis CI reports many app-schema unit test failures: >> https://s3.amazonaws.com/archive.travis-ci.org/jobs/207942836/log.txt >> >> Kind regards, >> -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Nuno Miguel Carvalho Oliveira @nmcoliveira Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 333 8128928 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e -mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. ------------------------------------------------------------------------------ Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition. http://sdm.link/oxford _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
