Re: [Geoserver-users] Returning any kind of file with WPS python script

a zip directly to you for a fast check? 2013/7/9 Andrea Aime > On Tue, Jul 9, 2013 at 2:18 PM, Fabrizio Tringali wrote: > >> Bitte Thomas, >> >> yes, my patch is just for the WPS plugin. I have no knowledge on the >> Python module, I want just alert you that i

Re: [Geoserver-users] Returning any kind of file with WPS python script

ver already output files as results > (RawOutput) so we we’re curious if this functionality can be used via the > Scripting Extension – in general the functionality of file results in the > WPS extension is already there as I observed… > > ** ** > > Thomas > > ** ** &g

Re: [Geoserver-users] Returning any kind of file with WPS python script

Thomas, Justin I developed some changes to an older version of GeoServer/GeoTools (2.2 / 8) in order to enable base64 complex objects management at the WPS level. I never found enough time to send a patch as required by current policies, but if you drop me a line I will share them with you and ma

Re: [Geoserver-users] WPS complex data results

lease consider the cross impact GT-GS) Any advice is welcome TIA, Fabrizio 2012/9/18 Andrea Aime > On Tue, Sep 18, 2012 at 4:56 PM, Fabrizio Tringali wrote: >> >> Looking for a reason in wps-core I found the method >> ExecuteProcessResponse.write(...), it seems that

[Geoserver-users] WPS complex data results

Hello everyone, I'm investigating about a difference between geoserver and deegree WPS. according to OGC WPS IS "If storage of a ComplexData output has not been requested via the ―asReference attribute (see Table 51), the ExecuteResponse document will contain that output. For ComplexData such as

Re: [Geoserver-users] REST security configuration on 2.2

GEOS-5139 Cheers, Fabrizio 2012/5/31 Andrea Aime > The approach suggested seems to work. > > In general I don't like rule systems that work based on rule order > (a-la iptables) > when it's also possible to apply a specificify approach, which does

[Geoserver-users] REST security configuration on 2.2

Hi everybody, I spent a day trying to setup REST security configuration (rest.properties) in a way that allows free access of a ROLE_X to workspace "abc" locking down others. Imho, securing the service by Ant patterns without an "ordered" list of rules is too difficult. I didn't find a way to sa