You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Rick Tessner <ri...@apache.org> on 2004/12/07 23:48:10 UTC
[help] Upgrading Cocoon in Forrest
Hi all,
I'm very close to being ready to committing a nice big patch to get
Forrest in line with the latest cocoon trunk (2.2.0-dev).
This included changes to the following:
* The Forrest java code now uses the Serviceable interfaces (ie. using
avalon.framework.service.* rather than avalon.framework.component.*)
* It appears JCS (used for stores) has been replaced with EHCache.
* The site: linkrewriting with jxpath 1.2 still doesn't work with the upgrade.
There's two issues I'm having.
First Issue: EHCache
---------------------
I am having a problem with the EHCache piece. When running a "forrest
site", a ton of DEBUG messages from EHCache appear on the screen rather
than being logged to the expected debug target.
Here's what I'm seeing (many many many lines like these):
<sample>
DEBUG 2004-12-07 14:41:06.973 [net.sf.e] (): Creating new CacheManager
with config URL:
jar:file:/home/rick/projects/forrest/van/lib/core/cocoon-2.2.0-dev.jar!/org/apache/cocoon/components/store/impl/ehcache.xml
</sample>
Does anyone with experience in cocoon / logging / cachestores have an idea
of what I can configure differently to make these go away?
Second Issue
-------------
Before I commit all this stuff, I'd like to have a good fallback point so
that if things are really messed up, we can say, do an "svn update -r
NNNNN" and things will be fine while we sort out the icky bits.
Right now, with the jxpath 1.2 in place, the site: URLs are not being
re-written properly. So, I'd like to roll that commit back and commit
with the older jxpath jars.
Then, with the updated cocoon in place in Forrest, we can figure out why
the LinkRewriter bits aren't working with the jxpath 1.2, contribute a
patch to cocoon (I believe that's where the LinkRewriter currently lives)
and then upgrade jxpath / cocoon.
Thoughts on the above two items?
--
Rick Tessner
rick at apache dot org
Re: [help] Upgrading Cocoon in Forrest
Posted by Antonio Gallardo <ag...@agssa.net>.
On Mie, 8 de Diciembre de 2004, 14:55, Nicola Ken Barozzi dijo:
> Antonio Gallardo wrote:
> ...
>> BTW, can we switch forrest to log4j?
>
> +0 I agree, it makes it easy to tell users how to sete up the graphical
> logger to see what is happening... if you do the change that is ;-)
Thanks, Nicola! I think is better start a VOTE, because this thread could
be "hidden" by some of us. ;-)
Best Regards,
Antonio Gallardo
Re: [help] Upgrading Cocoon in Forrest
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Antonio Gallardo wrote:
...
> BTW, can we switch forrest to log4j?
+0 I agree, it makes it easy to tell users how to sete up the graphical
logger to see what is happening... if you do the change that is ;-)
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [help] Upgrading Cocoon in Forrest
Posted by Antonio Gallardo <ag...@agssa.net>.
On Mar, 7 de Diciembre de 2004, 23:06, Dave Brondsema dijo:
> Quoting Rick Tessner <ri...@apache.org>:
>
>> * It appears JCS (used for stores) has been replaced with EHCache.
>>
>>
>> First Issue: EHCache
>> ---------------------
>>
>> I am having a problem with the EHCache piece. When running a "forrest
>> site", a ton of DEBUG messages from EHCache appear on the screen rather
>> than being logged to the expected debug target.
>>
>> Here's what I'm seeing (many many many lines like these):
>>
>> <sample>
>> DEBUG 2004-12-07 14:41:06.973 [net.sf.e] (): Creating new CacheManager
>> with config URL:
>>
> jar:file:/home/rick/projects/forrest/van/lib/core/cocoon-2.2.0-dev.jar!/org/apache/cocoon/components/store/impl/ehcache.xml
>> </sample>
>>
>> Does anyone with experience in cocoon / logging / cachestores have an
>> idea
>> of what I can configure differently to make these go away?
>>
>
> http://ehcache.sourceforge.net/documentation/#mozTocId265501 says its
> using
> Apache Commons logging, so the web.xml setting we did a while ago to get
> JCS
> commons-logging messages to go through Cocoon still applies (see
> http://wiki.apache.org/cocoon/JCSLogging).
I already tried this and don't work. BTW, can we switch forrest to log4j?
Best Regards,
Antonio Gallardo.
RE: [help] Upgrading Cocoon in Forrest
Posted by Alex Batlin <al...@batlin.com>.
Will this new version of cocoon include the session and authentication
framework blocks?
-----Original Message-----
From: Dave Brondsema [mailto:dave@brondsema.net]
Sent: 08 December 2004 05:06
To: dev@forrest.apache.org
Subject: Re: [help] Upgrading Cocoon in Forrest
Quoting Rick Tessner <ri...@apache.org>:
> * It appears JCS (used for stores) has been replaced with EHCache.
>
>
> First Issue: EHCache
> ---------------------
>
> I am having a problem with the EHCache piece. When running a "forrest
> site", a ton of DEBUG messages from EHCache appear on the screen rather
> than being logged to the expected debug target.
>
> Here's what I'm seeing (many many many lines like these):
>
> <sample>
> DEBUG 2004-12-07 14:41:06.973 [net.sf.e] (): Creating new CacheManager
> with config URL:
>
jar:file:/home/rick/projects/forrest/van/lib/core/cocoon-2.2.0-dev.jar!/org/
apache/cocoon/components/store/impl/ehcache.xml
> </sample>
>
> Does anyone with experience in cocoon / logging / cachestores have an idea
> of what I can configure differently to make these go away?
>
http://ehcache.sourceforge.net/documentation/#mozTocId265501 says its using
Apache Commons logging, so the web.xml setting we did a while ago to get JCS
commons-logging messages to go through Cocoon still applies (see
http://wiki.apache.org/cocoon/JCSLogging).
I don't have time to look at it tonight, but we can probably just modify
logkit.xconf to suppress the ehcache stuff some more.
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
http://csx.calvin.edu : student org
Re: [help] Upgrading Cocoon in Forrest
Posted by Dave Brondsema <da...@brondsema.net>.
Quoting Rick Tessner <ri...@apache.org>:
> * It appears JCS (used for stores) has been replaced with EHCache.
>
>
> First Issue: EHCache
> ---------------------
>
> I am having a problem with the EHCache piece. When running a "forrest
> site", a ton of DEBUG messages from EHCache appear on the screen rather
> than being logged to the expected debug target.
>
> Here's what I'm seeing (many many many lines like these):
>
> <sample>
> DEBUG 2004-12-07 14:41:06.973 [net.sf.e] (): Creating new CacheManager
> with config URL:
>
jar:file:/home/rick/projects/forrest/van/lib/core/cocoon-2.2.0-dev.jar!/org/apache/cocoon/components/store/impl/ehcache.xml
> </sample>
>
> Does anyone with experience in cocoon / logging / cachestores have an idea
> of what I can configure differently to make these go away?
>
http://ehcache.sourceforge.net/documentation/#mozTocId265501 says its using
Apache Commons logging, so the web.xml setting we did a while ago to get JCS
commons-logging messages to go through Cocoon still applies (see
http://wiki.apache.org/cocoon/JCSLogging).
I don't have time to look at it tonight, but we can probably just modify
logkit.xconf to suppress the ehcache stuff some more.
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
http://csx.calvin.edu : student org
Re: [help] Upgrading Cocoon in Forrest
Posted by David Crossley <cr...@apache.org>.
Juan Jose Pablos wrote:
> Rick Tessner wrote:
>
>> Hi all,
>>
>> I'm very close to being ready to committing a nice big patch to get
>> Forrest in line with the latest cocoon trunk (2.2.0-dev).
>>
>
> Funny, I was doing exactly the same around the same time. I will have a
> look tomorrow...
Rick gave us warning the other day that he was doing
this major operation.
--David
Re: [help] Upgrading Cocoon in Forrest
Posted by Juan Jose Pablos <ch...@apache.org>.
Rick Tessner wrote:
> Hi all,
>
> I'm very close to being ready to committing a nice big patch to get
> Forrest in line with the latest cocoon trunk (2.2.0-dev).
>
Funny, I was doing exactly the same around the same time. I will have a
look tomorrow...
Cheers,
Cheche
Re: [help] Upgrading Cocoon in Forrest
Posted by Antonio Gallardo <ag...@agssa.net>.
On Mar, 7 de Diciembre de 2004, 21:15, Rick Tessner dijo:
> Antonio Gallardo wrote:
>> Hi Rick,
>>
>> Thanks for the effort.
>>
>> Currently in lucene 1.4.1 exists a memory leak. It was fixed in 1.4.2. I
>> am right now testing in cocoon 2.2 the 1.4.3 version. Will be fine if
>> our
>> new cocoon snapshot include this fixes for lucene. ;-)
>
> D'oh! Just committed the cocoon upgrade. I think the hard work is done
> now, so it should be possible to upgrade Lucene as well once it's gone
> through testing in Cocoon. :)
No problem. We can update the lucene jar in forrest. It should not break
nothing. :-D
Best Regards,
Antonio Gallardo
Re: [help] Upgrading Cocoon in Forrest
Posted by Rick Tessner <ri...@apache.org>.
Antonio Gallardo wrote:
> Hi Rick,
>
> Thanks for the effort.
>
> Currently in lucene 1.4.1 exists a memory leak. It was fixed in 1.4.2. I
> am right now testing in cocoon 2.2 the 1.4.3 version. Will be fine if our
> new cocoon snapshot include this fixes for lucene. ;-)
D'oh! Just committed the cocoon upgrade. I think the hard work is done
now, so it should be possible to upgrade Lucene as well once it's gone
through testing in Cocoon. :)
> The test was already done for cocoon 2.1 and is working fine.
Good to hear that.
> Later I will try to fix the ehcache logs bug.
>
> WDYT?
That sounds fabulous Antonio. Thanks!
--
Rick Tessner
rick at apache dot org
Re: [help] Upgrading Cocoon in Forrest
Posted by Antonio Gallardo <ag...@agssa.net>.
Hi Rick,
Thanks for the effort.
Currently in lucene 1.4.1 exists a memory leak. It was fixed in 1.4.2. I
am right now testing in cocoon 2.2 the 1.4.3 version. Will be fine if our
new cocoon snapshot include this fixes for lucene. ;-)
The test was already done for cocoon 2.1 and is working fine.
Later I will try to fix the ehcache logs bug.
WDYT?
Best Regards,
Antonio Gallardo
On Mar, 7 de Diciembre de 2004, 16:48, Rick Tessner dijo:
> Hi all,
>
> I'm very close to being ready to committing a nice big patch to get
> Forrest in line with the latest cocoon trunk (2.2.0-dev).
>
> This included changes to the following:
>
> * The Forrest java code now uses the Serviceable interfaces (ie. using
> avalon.framework.service.* rather than avalon.framework.component.*)
> * It appears JCS (used for stores) has been replaced with EHCache.
> * The site: linkrewriting with jxpath 1.2 still doesn't work with the
> upgrade.
>
> There's two issues I'm having.
>
> First Issue: EHCache
> ---------------------
>
> I am having a problem with the EHCache piece. When running a "forrest
> site", a ton of DEBUG messages from EHCache appear on the screen rather
> than being logged to the expected debug target.
>
> Here's what I'm seeing (many many many lines like these):
>
> <sample>
> DEBUG 2004-12-07 14:41:06.973 [net.sf.e] (): Creating new CacheManager
> with config URL:
> jar:file:/home/rick/projects/forrest/van/lib/core/cocoon-2.2.0-dev.jar!/org/apache/cocoon/components/store/impl/ehcache.xml
> </sample>
>
> Does anyone with experience in cocoon / logging / cachestores have an idea
> of what I can configure differently to make these go away?
>
> Second Issue
> -------------
>
> Before I commit all this stuff, I'd like to have a good fallback point so
> that if things are really messed up, we can say, do an "svn update -r
> NNNNN" and things will be fine while we sort out the icky bits.
>
> Right now, with the jxpath 1.2 in place, the site: URLs are not being
> re-written properly. So, I'd like to roll that commit back and commit
> with the older jxpath jars.
>
> Then, with the updated cocoon in place in Forrest, we can figure out why
> the LinkRewriter bits aren't working with the jxpath 1.2, contribute a
> patch to cocoon (I believe that's where the LinkRewriter currently lives)
> and then upgrade jxpath / cocoon.
>
> Thoughts on the above two items?
>
> --
> Rick Tessner
> rick at apache dot org
>
Re: [help] Upgrading Cocoon in Forrest
Posted by David Crossley <cr...@apache.org>.
Rick Tessner wrote:
> David Crossley wrote:
>
>> Rick Tessner wrote:
>>
>>> David Crossley wrote:
>>>
>>>> +1 to reverting the jxpath jar change. Don't forget
>>>> the recent changes cocoon.xconf too.
>>>
>>>
>>>
>>> Do you mean that recent changes should be kept? Or backed out as well?
>>
>>
>>
>> Backed out as well. The whitespace changes were okay
>> but the following changes might have been part of
>> the new problems.
>> -------
>> - <exclude pattern="site:**"/>
>> - <exclude pattern="ext:**"/>
>> -
>> +
>> + <exclude pattern="**site:**"/>
>> + <exclude pattern="**ext:**"/>
>> -------
>
>
> Ahhhh ... back out the changes in cli.xconf ... not cocoon.xconf ...
Bleah, sorry for causing confusion.
--David
> Just tested with jxpath 1.2 & without the above cli.xconf changes.
> Still broken. :(
>
> Would really really like to get the jxpath upgraded to a released
> version. That'll be the next step after getting Forrest & Cocoon
> aligned. :)
>
Re: [help] Upgrading Cocoon in Forrest
Posted by Rick Tessner <ri...@apache.org>.
David Crossley wrote:
> Rick Tessner wrote:
>
>> David Crossley wrote:
>>
>>> +1 to reverting the jxpath jar change. Don't forget
>>> the recent changes cocoon.xconf too.
>>
>>
>> Do you mean that recent changes should be kept? Or backed out as well?
>
>
> Backed out as well. The whitespace changes were okay
> but the following changes might have been part of
> the new problems.
> -------
> - <exclude pattern="site:**"/>
> - <exclude pattern="ext:**"/>
> -
> +
> + <exclude pattern="**site:**"/>
> + <exclude pattern="**ext:**"/>
> -------
Ahhhh ... back out the changes in cli.xconf ... not cocoon.xconf ...
Just tested with jxpath 1.2 & without the above cli.xconf changes. Still
broken. :(
Would really really like to get the jxpath upgraded to a released version.
That'll be the next step after getting Forrest & Cocoon aligned. :)
--
Rick Tessner
rick at apache dot org
Re: [help] Upgrading Cocoon in Forrest
Posted by David Crossley <cr...@apache.org>.
Rick Tessner wrote:
> David Crossley wrote:
>
>> +1 to reverting the jxpath jar change. Don't forget
>> the recent changes cocoon.xconf too.
>
> Do you mean that recent changes should be kept? Or backed out as well?
Backed out as well. The whitespace changes were okay
but the following changes might have been part of
the new problems.
-------
- <exclude pattern="site:**"/>
- <exclude pattern="ext:**"/>
-
+
+ <exclude pattern="**site:**"/>
+ <exclude pattern="**ext:**"/>
-------
> Here's what I'm planning
>
> % cd $FORREST_HOME
> % svn --dry-run merge -r 109950:109949 .
> U main/webapp/WEB-INF/cli.xconf
> A lib/core/commons-jxpath-20030909.jar.license.txt
> A lib/core/commons-jxpath-20030909.jar
> D lib/core/commons-jxpath-1.2.jar.license.txt
> D lib/core/commons-jxpath-1.2.jar
>
> Or in english :)
>
> * reverse the change to cli.xconf.
> * Add commons-jxpath-2003*
> * Delete commons-jxpath-1.2*
>
Re: [help] Upgrading Cocoon in Forrest
Posted by Rick Tessner <ri...@apache.org>.
David Crossley wrote:
> +1 to reverting the jxpath jar change. Don't forget
> the recent changes cocoon.xconf too.
Do you mean that recent changes should be kept? Or backed out as well?
Here's what I'm planning
% cd $FORREST_HOME
% svn --dry-run merge -r 109950:109949 .
U main/webapp/WEB-INF/cli.xconf
A lib/core/commons-jxpath-20030909.jar.license.txt
A lib/core/commons-jxpath-20030909.jar
D lib/core/commons-jxpath-1.2.jar.license.txt
D lib/core/commons-jxpath-1.2.jar
Or in english :)
* reverse the change to cli.xconf.
* Add commons-jxpath-2003*
* Delete commons-jxpath-1.2*
--
Rick Tessner
rick at apache dot org
Re: [help] Upgrading Cocoon in Forrest
Posted by David Crossley <cr...@apache.org>.
Rick Tessner wrote:
[snip]
> Second Issue
> -------------
>
> Before I commit all this stuff, I'd like to have a good fallback point
> so that if things are really messed up, we can say, do an "svn update -r
> NNNNN" and things will be fine while we sort out the icky bits.
>
> Right now, with the jxpath 1.2 in place, the site: URLs are not being
> re-written properly. So, I'd like to roll that commit back and commit
> with the older jxpath jars.
>
> Then, with the updated cocoon in place in Forrest, we can figure out why
> the LinkRewriter bits aren't working with the jxpath 1.2, contribute a
> patch to cocoon (I believe that's where the LinkRewriter currently
> lives) and then upgrade jxpath / cocoon.
+1 to reverting the jxpath jar change. Don't forget
the recent changes cocoon.xconf too.
--David