The operations you want to perform may take some time, depending on the number of affected pages, so I wouldn't block the HTML request, triggered when you click the button, until the operation is done. Maybe this can help http://platform.xwiki.org/xwiki/bin/view/DevGuide/PerformingAsynchronousTas… . On Wed, Nov 25, 2015 at 12:47 PM, Giordano Ninonà < giordano.ninona(a)gmail.com huge to from runtime, truck _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hi Giordano, Maybe a quicker route for you to understand would be through Script Services [1]. You basically write a java component and then you write a facade (script service) for it which will be exposed to velocity code (that you usually write in a wiki page, executed server side). Your velocity code talks to the service which, in turn, talks to your java component. Sure, you could write all your java code directly in the service, but that`s not a very nice design, since these script services are not really intended to be used in java code (they are intended for scripts -- velocity, groovy, etc.) and, if you would need to re-use your code in java as well, a component is more suited that a script service (so you should do the heavy coding in the component). Finally, you write your wiki page using some velocity that handle the web logic, (e.g. maybe get some request parameters, do some computations, use some script services to perform more complex stuff and thus call java code, do some redirects, etc.) and finally print the html output to the browser that made the request. All of this is also mentioned in our devguide about writing components, maybe you`ve missed it [2]. However, as Marius hinted, the server side operations done in velocity (and the java code called by the velocity scripts) are performed synchronously, so the browser`s request needs to wait until all those operations finish and the html result is outputed. If your application's logic can not afford to wait for such a result to be computed, then you need to go the asynchronous path, with jobs and with interrogating the job`s status, providing progress information until it finishes executing. Hope this helps, Eduard P.S.: We are more than happy to receive help on the documentation side, specially in those places where it's sketchy and hard to understand, so you are encouraged to pitch in (since it's an open wiki where everyone can edit). I guess documentation is just like testing and it's quite a well known fact that developers are not perfect at testing their own code :) ---------- [1] http://extensions.xwiki.org/xwiki/bin/view/Extension/Script+Module [2] http://platform.xwiki.org/xwiki/bin/view/DevGuide/WritingComponents#HFromwi… On Wed, Nov 25, 2015 at 2:00 PM, Giordano Ninonà < giordano.ninona(a)gmail.com&gt; wrote: API triggered http://platform.xwiki.org/xwiki/bin/view/DevGuide/PerformingAsynchronousTas… the want that... _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs