5 Sep
2016
5 Sep
'16
9:59 a.m.
Hi Edward,
On 04 Sep 2016, at 19:26, Vincent Massol
<vincent(a)massol.net> wrote:
Hi Edward,
I’ve now committed the fix in http://jira.xwiki.org/browse/XWIKI-13678
Also, I’m getting the error you had, see
http://jira.xwiki.org/browse/XWIKI-13678?focusedCommentId=92572&page=co…
It’s a warning though so it doesn’t prevent XWiki from deploying.
We still need to figure out how to avoid it for a cleaner deployment.
Thanks
-Vincent
On 03 Sep 2016, at 13:45, Edward Knyshov
<edvorg(a)gmail.com> wrote:
I'm trying to inject xwiki logger using
@Inject
Logger logger;
But when I start xwiki I get totally broken app and following errors in my
logs:
https://gist.github.com/edvorg/f6d5205b51ae32b71faf527d9a80302c
Has anybody met this before?
Thanks, Edward.
This could be a classloading issue. JBoss/Wildfly has been to know to be quite bad in the
past at isolating classloaders by default. What could happen is that some plexus version
and configuration is done by Wildfly that interferes with the XWiki webapp.
I’ve tried to reproduce the issue by downloading and starting xwiki in Wildfly
10.1.0.Final (servlet only) and hit another classloader problem:
https://gist.github.com/vmassol/2f0d9014858cd8f73892a7166382f416
From what I could see the problem is that the javax.xml.bind JAR is not present in
Wildfly 10.1.0.Final (servlet only). So I downloaded and installed the full JavaEE one and
it went further (note to self: find and document how to make the servlet only version
work) but I still got an error:
https://gist.github.com/vmassol/8f176418af6bfbae173e06d45dcab34a
I was able to solve this by telling Wildfly to disable implicit bean archives, see
https://docs.jboss.org/author/display/WFLY10/CDI+Reference
I added a META-INF/jboss-all.xml with the following content:
<jboss xmlns="urn:jboss:1.0">
<weld xmlns="urn:jboss:weld:1.0"
require-bean-descriptor="true"/>
</jboss>
Note to self: open a jira issue and commit this to make the XWiki WAR ready for wildfly
deployment. Then it worked :) There are of course a lot of
warnings but no error.
So I didn’t get your error it seems.
Thanks
-Vincent