Is there any way to make Xwiki's error messages more developer-friendly...
because one stupid missing character in velocity, in javascript, in groovy,
etc, and the evaluation of the page blows up. Unfortunately, it just dies
with a general error, not even telling you the last line at which it was
still parsing in a sane-state. Sometimes to get things working you have to
resort to commenting out large portions of text just to find where the error
is. Or using "breadcrumbs"
(html, or javascript alert()) to figure out how far it got in the page.
Granted, the biggest help is to have syntax assisted editing -- which at
least prevents mismatched parentheses- and quotation-errors. ... which is
why I use vtl-mode in emacs (velocity template language minor mode) and then
switch between javascript, html, or normal for major-mode... and then just
cut/paste into xwiki.
IMHO, a great future feature is a 'subversion' "publishing bridge" for
xwiki, which would let you checkin/checkout a xwiki file in subversion on
your local workstation (e.g. using emacs built in subversion intfc, or
eclipse's). On the server-end, instead of actually checking in a revision
using 'subversion', an xwiki document would be created (or versioned)
instead.
Niels
http://nielsmayer.com
On Thu, Apr 2, 2009 at 4:04 AM, Jerome Velociter <jerome(a)xwiki.com> wrote:
Asiri Rathnayake wrote:
Hi
On Thu, Apr 2, 2009 at 4:09 PM, walido <walid.kharroubi(a)hraccess.com>
wrote:
>
> Hi,
> thanks for your fast answer here's the code of the class
> (exuse me i don't know how to use the pastebin or tinybin thing)
>
> * Groovy Class #* */
Looks like a slash is missing here, it should be:
/* Groovy Class #* */
not
* Groovy Class #* */