You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Steinar Rune Eriksen <sr...@bizpartner.no> on 2004/09/24 13:29:31 UTC
Problems on JBoss 4.0 release version
I've been using Cocoon 2.1.5.1 successfully on JBoss 4 RC1 and RC2 for a
while. Very few issues at all actually. I just had to swap the Castor
versions and put commons-logging into jboss/server/default/lib and it
worked fine.
However, on JBoss 4. final release I get some more serious problems. It
complains about org/apache/log/Logger not found, and of course this JAR
will want a lot of other dependent Jars so it becomes a bit more messy
to handle/install.
Anyone else experienced the same, and found a simple way around it?
Steinar
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Problems on JBoss 4.0 release version
Posted by Petri Wessman <or...@orava.org>.
On Monday 27 September 2004 10:26, Leszek Gawron wrote:
> Upayavira wrote:
> > Steinar Rune Eriksen wrote:
> >> I've been using Cocoon 2.1.5.1 successfully on JBoss 4 RC1 and RC2 for
> >> a while. Very few issues at all actually. I just had to swap the
> >> Castor versions and put commons-logging into jboss/server/default/lib
> >> and it worked fine.
> >>
> >>
> >> However, on JBoss 4. final release I get some more serious problems.
> >> It complains about org/apache/log/Logger not found, and of course this
> >> JAR will want a lot of other dependent Jars so it becomes a bit more
> >> messy to handle/install.
> >> Anyone else experienced the same, and found a simple way around it?
I managed to get the Cocoon demo webapp to work with JBoss 4.0 by moving some
jars around. This seemed to work:
- Move logkit-1.2.2.jar from the Cocoon webapp WEB-INF/lib to JBoss
server/default/lib (assuming you're using the "default" server). Move, not
copy :)
- Remove commons-logging-1.0.4.jar and log4j-1.2.8.jar from the Cocoon webapp
WEB-INF/lib
Things seemed to work ok after that, though I haven't done extensive testing.
My own website at http://www.orava.org is running Cocoon (CVS snapshot) and
JBoss 4.0 at the moment and things are fine, but I'm not doing anything very
fancy Cocoon-wise.
Hope that helps.
//Petri
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Problems on JBoss 4.0 release version
Posted by Leszek Gawron <lg...@mobilebox.pl>.
Upayavira wrote:
> Steinar Rune Eriksen wrote:
>
>> I've been using Cocoon 2.1.5.1 successfully on JBoss 4 RC1 and RC2 for
>> a while. Very few issues at all actually. I just had to swap the
>> Castor versions and put commons-logging into jboss/server/default/lib
>> and it worked fine.
>>
>>
>> However, on JBoss 4. final release I get some more serious problems.
>> It complains about org/apache/log/Logger not found, and of course this
>> JAR will want a lot of other dependent Jars so it becomes a bit more
>> messy to handle/install.
>> Anyone else experienced the same, and found a simple way around it?
>
>
> I something similar using Jetty 5.0, which I suspect is a part of
> JBoss4. A problem to do with logging. I'd suggest mentioning it on the
> dev list, but do quote a full stack trace, as that will help a lot.
>
> My solution I'm afraid was to go back to Jetty 4.2.
Also had loggers problem. Jetty 5.0 uses commons logging and that is the
source of the problem.
Maybe this would help (haven't tried - just found on wiki):
add
-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger
to the command line.
add
<init-param>
<param-name>force-property</param-name>
<param-value>
org.apache.commons.logging.Log=org.apache.commons.logging.impl.LogKitLogger
</param-value>
</init-param>
to web.xml
I was able to run jetty with
org.apache.commons.logging.Log=org.apache.commons.logging.impl.LogKitLogger on
command line but then LogKitLogger had no config and logged everything in
DEBUG - nightmare :)
I am still with Jetty 4.2
--
Leszek Gawron lgawron@mobilebox.pl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Problems on JBoss 4.0 release version
Posted by Norman Barker <no...@comsine.co.uk>.
Hi,
was this ever resolved? I tried to upgrade to JBoss 4.0.0 today, and
got the same error, I also fiddled with
the classpath but to no effect.
Problem is using Cocoon 2.1.5 with JBoss 3.2.3 effectively reduces JBoss
to just a servlet engine since upgrading
the XML libraries for Cocoon disables the JMS and JNDI in JBoss 3.2.3.
This isn't the case in JBoss AS (4.0.0)
since the XML libraries are the same, it is just the Apache Logger error
as reported below.
Any help would be greatly appreciated.
Norman
Upayavira wrote:
> Steinar Rune Eriksen wrote:
>
>> I've been using Cocoon 2.1.5.1 successfully on JBoss 4 RC1 and RC2
>> for a while. Very few issues at all actually. I just had to swap the
>> Castor versions and put commons-logging into
>> jboss/server/default/lib and it worked fine.
>>
>>
>> However, on JBoss 4. final release I get some more serious problems.
>> It complains about org/apache/log/Logger not found, and of course
>> this JAR will want a lot of other dependent Jars so it becomes a bit
>> more messy to handle/install.
>> Anyone else experienced the same, and found a simple way around it?
>
>
> I something similar using Jetty 5.0, which I suspect is a part of
> JBoss4. A problem to do with logging. I'd suggest mentioning it on the
> dev list, but do quote a full stack trace, as that will help a lot.
>
> My solution I'm afraid was to go back to Jetty 4.2.
>
> Regards, Upayavira
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
--
Norman Barker
Software Engineer
ComSine Ltd
Tel: +44 (0)1483 457121
Web: http://www.comsine.com
*Please Note:*
This text is confidential. If you are not the named addressee, it could be unlawful for you to read, copy, distribute, disclose or use the information contained herewith. If you are not the intended recipient please telephone +44(0)1483 457121.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Problems on JBoss 4.0 release version
Posted by Upayavira <uv...@upaya.co.uk>.
Steinar Rune Eriksen wrote:
> I've been using Cocoon 2.1.5.1 successfully on JBoss 4 RC1 and RC2 for
> a while. Very few issues at all actually. I just had to swap the
> Castor versions and put commons-logging into jboss/server/default/lib
> and it worked fine.
>
>
> However, on JBoss 4. final release I get some more serious problems.
> It complains about org/apache/log/Logger not found, and of course this
> JAR will want a lot of other dependent Jars so it becomes a bit more
> messy to handle/install.
> Anyone else experienced the same, and found a simple way around it?
I something similar using Jetty 5.0, which I suspect is a part of
JBoss4. A problem to do with logging. I'd suggest mentioning it on the
dev list, but do quote a full stack trace, as that will help a lot.
My solution I'm afraid was to go back to Jetty 4.2.
Regards, Upayavira
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org