Hi Ben, Thanks for the feedback.
| It will be tricky to test that there is no unintended cross-communication between the isolated workspaces. Yeah I agree this will b tricky to test. Kind regards, Nuno Oliveira On 02/12/2017 11:06 PM, Ben Caradoc-Davies wrote: > Nuno, > > I accept that a full namespace/workspace information model refactoring > is too expensive. It would also be backwards-incompatible for all > users; I think this is not justified for a change that would benefit > only app-schema users. I am comfortable with your more modest > improvement. > > Yes, an app-schema store can contain multiple mapping for the same type: > http://docs.geoserver.org/latest/en/user/data/app-schema/feature-chaining.html#multiple-mappings-of-the-same-type > > > > If the isolated feature type is not visible at the top level and is > only published as a nested type, could it be mapped entirely using the > nested mapping mechanism, without any changes to workspaces? What > functionality would isolated workspaces provide that cannot be > delivered with nested mappings? Your original email contains the > answer: delivering the same type more than once via virtual services. > > This sounds like a useful improvement, and your approach seems > reasonable. It will be tricky to test that there is no unintended > cross-communication between the isolated workspaces. > > Kind regards, > Ben. > > > On 11/02/17 04:19, Nuno Oliveira wrote: >> Hi Ben, >> >> | Stop me now, I am just getting started! >> >> Ahaha thanks for the detailed feedback :) >> >> Long story short, I know the deeper problem but I (we) can't afford the >> perfect solution. The solution I proposed is not perfect and will >> certainly not fix all the current problems between app-schema and >> workspaces but will allow users to publish the same feature type >> multiple times (this is not an app-schema exclusive issue) and avoid >> having several GeoServer instances just for that propose. >> >> In a strict GeoServer point view isolated workspaces can repeat name >> spaces and will make their resources only available in their scope and >> will give preference to their own resources when looking for a certain >> resource. The consequence of this is that it will be possible to publish >> the same feature type (name space + name) multiple times. >> >> For GeoServer app-schema is a normal data store and app-schema on is >> side doesn't know anything about GeoServer workspaces. The problem on >> app-schema side is that mappings are no considered by store but instead >> globally, the main reason for this was feature chaining right ? So when >> we search the mappings for a certain feature type (XML element) the >> AppSchemaDataAccessRegistry singleton will look in all the defined >> app-schema stores and return the first one he founds. >> >> An app-schema data store can contain mappings for multiple types right ? >> So I propose to change the AppSchemaDataAccessRegistry in sort that he >> will give preference to mappings defined in the same store and only if >> the desired mapping is not found in the same store we will search >> globally. This way it will be possible to define different mappings for >> a feature type (XML element) and publish them in GeoServer in isolated >> workspaces. >> >> What do you think about this ? > -- == 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. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
