4 May
2011
4 May
'11
1:21 p.m.
On 05/04/2011 02:04 AM, Sergiu Dumitriu wrote:
On 05/04/2011 01:54 AM, andyp wrote:
OK, I have an answer.
The stacktraces you get are not really a problem. As you can see, those
are WARN messages. You can safely ignore those. They are caused by the
fact that we're mixing 1.0 and 1.4 jackrabbit modules, and some of the
classes have changed their signatures. This is not a problem, since
we're not actually using those classes that are incompatible.
Starting JBoss take a looooot of time (12+ minutes on my machine), so be
patient when loading. You must wait until the startup script prints a
message like this:
Hi Sergiu,
If I try that I get the same class loading error and JBoss is unable to
start:
I'll download a JBoss and try for myself, since debugging over the email
is quite slow.
Unfortunately it's quite late for me, I'll try it tomorrow and reply
with the outcome.
Just to make sure, you're using JBoss Application Server 6.0.0, the
community edition, right? 13:09:00,862 INFO
[org.jboss.bootstrap.impl.base.server.AbstractServer] JBossAS [6.0.0.Final
"Neo"] Started in 12m:17s:88ms
There is another real error that occurs, and it's caused by a bad jar
file. You must solve it manually:
- locate WEB-INF/jaxb-xjc-2.1.8.jar
- delete the 1.0 directory from it (for example you can extract, delete
and repack the jar)
Right now I don't get any more class loading errors, but I still have an
error about the missing data source, maybe I didn't configure it correctly:
Deployment
"jboss-switchboard:appName=xwiki,module=xwiki" is missing the following
dependencies:
Dependency "java:jdbc/XWikiDS" (should be in state "Installed",
but is actually in state "** NOT FOUND Depends on 'java:jdbc/XWikiDS'
**")
--
Sergiu Dumitriu
http://purl.org/net/sergiu/