I guess it means the code that gets the list of available syntaxes is
only looking at root component manager instead of context component
manager (in you case I guess you installed it on main wiki and not "on
farm").
On Fri, May 23, 2014 at 2:49 PM, Jeremie BOUSQUET
<jeremie.bousquet(a)gmail.com> wrote:
Dear community,
I wanted to test the apt/1.0 syntax, so I updated xwiki.cfg to add
"apt/1.0" in parameter "xwiki.rendering.syntaxes" and restarted my
wiki.
When editing a page, no "apt/1.0" choice appeared in the Document Syntax
Panel.
So in another page I displayed the available parsers and renderers, which
gave:
Parsers : [XWiki 2.1, Markdown 1.0, XWiki 2.0, TWiki 1.0, XWiki 1.0,
JSPWiki 1.0, MediaWiki 1.0, DocBook 4.4, HTML 4.01, XHTML 1.0, Creole 1.0,
Confluence 1.0, Plain 1.0]
Renderers : [DocBook 4.4, TeX 1.0, XWiki 2.1, Annotated XHTML 1.0, XWiki
2.0, XHTML 1.0, XHTML Macro 1.0, Plain 1.0]
(I'm on 5.1, apt was added in 4.3, so it should be there unless it was
removed later and I missed the release note - or there was an error during
install/upgrade but it seems unlikely)
So from Extension Manager, I searched and installed
org.xwiki.rendering:xwiki-rendering-syntax-apt-5.1.jar.
No change on the list of parsers/renderers, still no APT.
I thought that probably renderers and parsers are registered only at start
and maybe not by EM, so I restarted the wiki again, but no change on the
list of parsers/renderers.
Eventually I moved that jars (for xwiki-rendering-syntax-apt and
xwiki-rendering-xml) from the extension repository under perm data dir, to
WEB-INF/lib of the webapp, and restarted again, and apt now appears in the
list of parsers/renderers !
Then I tried to enter some content in a page, with apt syntax, and on
saving got this:
Caused by: java.lang.NoClassDefFoundError:
org/apache/maven/doxia/module/apt/AptParser
at
org.xwiki.rendering.internal.parser.apt.APTParser.createDoxiaParser(APTParser.java:50)
~[xwiki-rendering-syntax-apt-5.1.jar:na]
at
org.xwiki.rendering.internal.parser.doxia.AbstractDoxiaParser.parse(AbstractDoxiaParser.java:99)
~[xwiki-rendering-syntax-doxia-5.1.jar:na]
at
org.xwiki.rendering.internal.parser.doxia.AbstractDoxiaParser.parse(AbstractDoxiaParser.java:70)
~[xwiki-rendering-syntax-doxia-5.1.jar:na]
at
com.xpn.xwiki.doc.XWikiDocument.parseContent(XWikiDocument.java:7975)
~[xwiki-platform-legacy-oldcore-5.1.jar:na]
[...]
... 50 common frames omitted
... though from EM, dependencies of the apt renderer seem to be correctly
installed (either provided or installed) :
XWiki Rendering - Syntax - Doxia Bridge5.1 (in wiki xwiki) Provided
Doxia :: APT Module1.3 (in wiki xwiki) Installed
XWiki Rendering - Legacy - API5.1 (in wiki xwiki) Provided
XWiki Commons - Legacy - Component - API5.1 (in wiki xwiki) Provided
doxia-module-apt-1.3.jar is present in extensions repo (under data dir), so
I thought maybe it had to be present in WEB-INF/lib (though it seems
surprising that it could cause an error, never had those kind of
classloader issue with xwiki extensions). So I moved it to WEB-INF/lib and
restarted and .... now it's ok. Just tested with a page, and the result is
very nice ! :)
To be complete, I checked in war file of 6.0.1, and
xwiki-rendering-syntax-apt-6.0.1.jar is not present. So I suppose APT
format has not be much used yet ;-)
Thanks,
Jeremie
PS: I would love to be able to publish a maven site to XWiki ... But I
think parsing APT from xwiki may not be the best, as the idea is not to
edit a maven site from xwiki (at least, my purpose is to view published
maven sites, you could use apt parser to edit maven sites sources). What I
would like is to be able to view a maven site from a site packaged in a jar
in a maven repository, and use xwiki as a front-end for maven sites - that
would be cool (or publish those jars into xwiki as attachments, so they
would be indexed by solr)
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users