[Geoserver-devel] Various fixes for GeoServer GUI + JDBCConfig plugin

GeoServer GeoServer Developer
1

Hi all,

I would like to submit to your attention the following pull request which contains various improvements on the GeoServer GUI, especially useful when the JDBCConfig plugin is active.

Here is the link to my pull request: https://github.com/geoserver/geoserver/pull/836.

These improvements can be noticed with an high number of Layers and stores configured.

The various improvements are quickly summarized here:

  1. Improved the performances of the LayerPreview

  2. Improved the StoreProvder class

  3. Improved the StyleProvder class

  4. Improved the performances of the LayerListPanel

  5. Reduced the GWC startup time by adding a lazy loading of the GeoServerTileLayers

  6. Fixed an issue on the SecuredCatalog which actually does not create a security filter for the Styles

  7. Changed the DefaultDataAccessManager into a DefaultResourceAccessManager

  8. For JDBCConfig plugin, improved the query construction and added a few nested properties for speeding up db queries.

I will be pleased to answer to your questions. For what concerns the modifications on the DefaultDataAccessManager, it should be better to ask Andrea which has worked on that class.

Thank you for your attention.
Regards,
Nicola Lagomarsini.

···

==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

Ing. Nicola Lagomarsini
Junior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272

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.

2

On Fri, Nov 28, 2014 at 8:11 PM, Nicola Lagomarsini <
nicola.lagomarsini@anonymised.com> wrote:

I will be pleased to answer to your questions. For what concerns the
modifications on the DefaultDataAccessManager, it should be better to ask
Andrea which has worked on that class.

Well, in short, that complex security filter function was actually
necessary... but it was not impossible to remove and optimize.
The thing is, it was there because the default security subsystem of
GeoServer was still using a DataAccessManager.

To fix thing, I've upgraded that class to become a
DefaultResourceAccessManager, and build security filters according to
the security tree structure, and paying attention to keep the filters
encodable:
https://github.com/geosolutions-it/geoserver/blob/fixGUIPerformances/src/main/src/main/java/org/geoserver/security/impl/DefaultResourceAccessManager.java#L252

In order to achieve that, I've also had to add support for
PropertyIsNotEqualTo in the filter to sql encoder (which declared such
support, but did not
implement it).

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

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.

-------------------------------------------------------