I do remember bringing up the idea of making processes a first class citizen in the catalog. Basically come up with a ProcessInfo and extends ResourceInfo and then be able to use data security to apply access rules to them. Is that what you're talking about here? I am thinking maybe not?
On Thu, Oct 23, 2014 at 3:53 AM, Andrea Aime <[email protected]> wrote: > On Thu, Oct 23, 2014 at 11:08 AM, Andrea Aime < > [email protected]> wrote: > >> And then change the current user interface to work against the property >> files, and allow the specification or role lists on a per process basis, >> instead of a simple on/off checkbox. >> I'm leaning towards the second, what do you think? >> > > As a possible interesting alternative, we can forget about the property > file, and work off the existing on/off process configuration, > which is based on the following interface: > > public interface ProcessGroupInfo extends Info, Cloneable { > > /** > * The process factory class (only means to identify it) > */ > public Class<? extends ProcessFactory> getFactoryClass(); > > /** > * Sets the process factory class > * > * @param factoryClass > */ > public void setFactoryClass(Class<? extends ProcessFactory> > factoryClass); > > /** > * True if the factory is enabled, false otherwise > * > * @return > */ > public boolean isEnabled(); > > /** > * Enables/disables the factory > * > * @param enabled > */ > public void setEnabled(boolean enabled); > > /** > * The list of processes generated by this factory that needs to be > filtered out (disabled) > * > * @return > */ > public List<Name> getFilteredProcesses(); > > /** > * The metadata map, can contain any sort of information that non core > plugins might use to > * handle information related to this factory > * > * @return > */ > MetadataMap getMetadata(); > > /** > * Creares a copy of this class > * @return > */ > ProcessGroupInfo clone(); > > } > > In order to maintain backwards compatibility we could extend it so that: t > has a list of roles that can access it (when enabled). > And then the list of process names being filtered could be replaced by a > list of ProcessInfo beans (something that Justin > was pushing for when we discussed the ability to turn on and off > processes) that do contain, for the time being, > a on/off flag, and a list of roles that can access them, but could be > expanded later to also contain process limits. > > It builds on what we have, and keeps this configuration integrated with > the main WPS config, making it > also readily available for REST usage. > > 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. > > ------------------------------------------------------- > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Geoserver-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > > -- Justin Deoliveira VP Engineering | Boundless <http://boundlessgeo.com/> [email protected] @boundlessgeo <http://twitter.com/boundlessgeo/>
------------------------------------------------------------------------------
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
