16 Aug
2014
16 Aug
'14
10:31 p.m.
Hi Vincent,
Le 16 août 2014 21:42, "vincent(a)massol.net" <vincent(a)massol.net> a écrit
:
On 5 Aug 2014 at 15:48:27, Jeremie BOUSQUET (jeremie.bousquet(a)gmail.com
(mailto:jeremie.bousquet@gmail.com)) wrote:
> Hello XWiki Community,
>
> Got some issue with executing groovy in a page ...
>
> I have a page with a groovy class, that needs some jars dependencies.
> The following "works":
>
> {{groovy jars="attach:toto.jar,..."}}
>
> import ...
>
> public class MyClass {
> ...
> }
>
> def myobj = new MyClass()
> // do something with myobj ...
> {{/groovy}}
>
> Then I'd like to execute this code from another page.
> So I removed the {{groovy}} macro tags and the isolated code at the end,
> leaving only the class declaration and imports.
> From the other page I use the following version of parseGroovyFromPage:
>
http://maven.xwiki.org/site/docs/xwiki-javadoc-4.1.x/com/xpn/xwiki/api/XWik…
Why not keep the {{groovy}} macro and instead use {{include
reference=“…”/}} from
the calling page? Using parseGroovyFromPage is the
old way of doing it.
Right, but in a scheduler job I can only put groovy, not wiki syntax, isn't
it ?
Thanks
-Vincent
> I provide it with the name of the page containing my groovy class, twice
> (once for the script and once for the jars).
> It results in a page loading infinitely until it time-outs ... From the
> logs it seems my class never gets executed.
>
> Any idea ?
>
> Note: I think it's a "crappy" method, and I plan to put this as a
java
> component, but in a "proof of concept" stage the groovy script is very
> useful.
>
> Thanks,
> Jeremie