On Fri, May 10, 2019 at 12:02 AM Chris Hodgson <[email protected]> wrote:
> I agree, getting caught up in ideals and "perfection" prevents you from > moving forward with basic function. > > Also I know the source is really the ultimate developer documentation, and > any attempt at developer docs always gets stale. But as the code gets > bigger, it gets harder to find relevant examples. I went through all of the > other community modules and none of them were doing something like what I > was trying to do for MapML. > Rule of thumb: never look in community modules unless you have to. They are un-maintained, have never been checked by a larger group, can be stale, if they have been around for a while they will likely not pass their tests, they are not subject to QA checks either (e.g. spotbugs, errorprone, pmd). Check core modules and extensions instead, they have a better chance of containing suitable example (they are not gold plated mind, but the average supported module is in better shape than the average community module, exceptions might exist in both directions). > The pointers to examples is exactly what I'm going for with the idea of > listing the extension points - if you at least have those names, you can > look for implementations, and you have a nice entry point into the code. I > was already aware of the output format extension points so those were > relatively easy to find and mimic. When I saw that the REST module was > using Spring MVC, and I've recently been building Spring MVC REST APIs, I > thought that's all I needed to know to be off and running. Apparently I > know just enough Spring to be dangerous ;) > See above about not assuming GeoServer behaves like a recent/small app. If you need to extend the REST API gs-restconfig is your "bible", there are a number of other extension modules contributing to it too. > Anyways, just wondering if there is a way to turn my recent experience > with Geoserver development (as someone who has typically been more a user > of Geoserver as well as a GIS-oriented Java developer) into something > useful for those who follow (docs or otherwise). > Minimal docs listing extension points and significant usage points are likely useful. Or even just a summary of these mails, showing people how to gather the information they need. Other things that could be useful in terms of information gathering are significant breakpoints to add in a debug session to learn how the code works step by step (I personally do that a lot) 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-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
