You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Gerhard Froehlich <g-...@gmx.de> on 2001/12/07 02:51:35 UTC
Branches and CachingxxxPipline enlightenment request!
Hi,
I did 2 checkouts:
1. HEAD:
The system is using NonCachingxxxPipelines! I've looked into the
cocoon.xconf but there are the caching ones configured (cocoon.roles
don't have any Pipline role definition).
2. cocoon_20
The system is using CachingxxxPipelines *relief* as configured in the
cocoon.xconf file and Caching is working and the Store system swaps
laboriously CachedxxxObjects out to the fs, etc.
I don't understand why the system is using the NonCachingxxxPipelines
in 1) (seems like Vodoo to me ;) and if there is some higher meaning, why?
The problem is, that this caused some confusion here last days.
(and this days not only upon me ;-).
A second more personal request are those various branches in the
CVS repository. I lost a little bit the track to the cocoon release
plans. I did a "cvs status -v someclass" and got this list:
cocoon_20 (revision: 1.2.2.22)
-> actual distribution
cocoon_20_rc2 (revision: 1.2.2.20)
-> expired or still used?
cocoon_20_rc1 (revision: 1.2.2.17)
-> expired or still used?
cocoon_20_b2 (revision: 1.2.2.6)
-> actual development?
cocoon_20_branch_mergepoint (revision: 1.2)
-> expired or still used?
cocoon_20_branch (branch: 1.2.2)
->expired or still used?
cocoon_20_b1 (revision: 1.2)
->expired or still used?
Could somebody with enough Cocoon karma give me some
enlightenment, please?!
Cheers
Gerhard
--------------------------------
Beam me up... arrgh, no carrier!
--------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Branches and CachingxxxPipline enlightenment request!
Posted by Sylvain Wallez <sy...@anyware-tech.com>.
giacomo a écrit :
>
<snip/>
> >
> > This is now fixed, and I also copied roles in sitemap.roles to
> > cocoon.roles. This allows pipeline declarations to be taken into account
> > as expected.
> >
> > But I'm not happy with declaring sitemap-specific roles in cocoon.roles,
> > and I'll propose a cleaner solution later (I'm a bit overworked now).
>
> I don't know why the pipeline roles are defined in the sitemap.roles
> file. They are configured in the cocoon.xconf file and thus their roles
> should be in the cocoon.roles file, don't you think so?
>
> Giacomo
Sure. I committed new changes :
- Pipelines are now Recomposable : this what they actually ever were,
since sitemap.xsl changes their component manager,
- Selectors are lazily looked up in AbstractXxxPipeline, meaning the use
the component manager set with recompose(),
- this allows for Pipeline & Connector roles to be only in cocoon.roles
and xxxxSelector roles only in sitemap.roles
... and I'm happier with these changes ;)
Sylvain
--
Sylvain Wallez
Anyware Technologies - http://www.anyware-tech.com
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Branches and CachingxxxPipline enlightenment request!
Posted by giacomo <gi...@apache.org>.
On Fri, 7 Dec 2001, Sylvain Wallez wrote:
>
>
> Gerhard Froehlich a écrit :
> >
> > Hi,
> > I did 2 checkouts:
> >
> > 1. HEAD:
> > The system is using NonCachingxxxPipelines! I've looked into the
> > cocoon.xconf but there are the caching ones configured (cocoon.roles
> > don't have any Pipline role definition).
>
> That's me who introduced this bug when componentizing the sitemap
> engine. This required moving roles defined in sitemap.roles to
> cocoon.roles, but after that, Cocoon crashed and I wasn't able to find
> the cause. So I left the roles in sitemap.roles, but this had the effect
> of always using the default pipeline classes specified in sitemap.roles,
> hence the NonCachingPipelines.
>
> But I finally found the cause of the crash ! In sitemap.xsl, pipelines
> weren't composed with the sitemap component manager on external request,
> thus the crash.
>
> This is now fixed, and I also copied roles in sitemap.roles to
> cocoon.roles. This allows pipeline declarations to be taken into account
> as expected.
>
> But I'm not happy with declaring sitemap-specific roles in cocoon.roles,
> and I'll propose a cleaner solution later (I'm a bit overworked now).
I don't know why the pipeline roles are defined in the sitemap.roles
file. They are configured in the cocoon.xconf file and thus their roles
should be in the cocoon.roles file, don't you think so?
Giacomo
> > 2. cocoon_20
> > The system is using CachingxxxPipelines *relief* as configured in the
> > cocoon.xconf file and Caching is working and the Store system swaps
> > laboriously CachedxxxObjects out to the fs, etc.
> >
> > I don't understand why the system is using the NonCachingxxxPipelines
> > in 1) (seems like Vodoo to me ;) and if there is some higher meaning, why?
> >
> > The problem is, that this caused some confusion here last days.
> > (and this days not only upon me ;-).
>
> Sorry for all this confusion :/
>
> > A second more personal request are those various branches in the
> > CVS repository. I lost a little bit the track to the cocoon release
> > plans. I did a "cvs status -v someclass" and got this list:
> > cocoon_20 (revision: 1.2.2.22)
> > -> actual distribution
> > cocoon_20_rc2 (revision: 1.2.2.20)
> > -> expired or still used?
> > cocoon_20_rc1 (revision: 1.2.2.17)
> > -> expired or still used?
> > cocoon_20_b2 (revision: 1.2.2.6)
> > -> actual development?
> > cocoon_20_branch_mergepoint (revision: 1.2)
> > -> expired or still used?
> > cocoon_20_branch (branch: 1.2.2)
> > ->expired or still used?
> > cocoon_20_b1 (revision: 1.2)
> > ->expired or still used?
> >
> > Could somebody with enough Cocoon karma give me some
> > enlightenment, please?!
>
> You're mixing branches and tags. There are only two branches : HEAD and
> cocoon_20_branch, all other names are tags that label the various
> releases or important points in the project life.
>
> > Cheers
> > Gerhard
> >
> > --------------------------------
> > Beam me up... arrgh, no carrier!
> > --------------------------------
> Personal request : where do all these sentences come form ?
>
> Sylvain
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Branches and CachingxxxPipline enlightenment request!
Posted by Sylvain Wallez <sy...@anyware-tech.com>.
Gerhard Froehlich a écrit :
>
> Hi,
> I did 2 checkouts:
>
> 1. HEAD:
> The system is using NonCachingxxxPipelines! I've looked into the
> cocoon.xconf but there are the caching ones configured (cocoon.roles
> don't have any Pipline role definition).
That's me who introduced this bug when componentizing the sitemap
engine. This required moving roles defined in sitemap.roles to
cocoon.roles, but after that, Cocoon crashed and I wasn't able to find
the cause. So I left the roles in sitemap.roles, but this had the effect
of always using the default pipeline classes specified in sitemap.roles,
hence the NonCachingPipelines.
But I finally found the cause of the crash ! In sitemap.xsl, pipelines
weren't composed with the sitemap component manager on external request,
thus the crash.
This is now fixed, and I also copied roles in sitemap.roles to
cocoon.roles. This allows pipeline declarations to be taken into account
as expected.
But I'm not happy with declaring sitemap-specific roles in cocoon.roles,
and I'll propose a cleaner solution later (I'm a bit overworked now).
> 2. cocoon_20
> The system is using CachingxxxPipelines *relief* as configured in the
> cocoon.xconf file and Caching is working and the Store system swaps
> laboriously CachedxxxObjects out to the fs, etc.
>
> I don't understand why the system is using the NonCachingxxxPipelines
> in 1) (seems like Vodoo to me ;) and if there is some higher meaning, why?
>
> The problem is, that this caused some confusion here last days.
> (and this days not only upon me ;-).
Sorry for all this confusion :/
> A second more personal request are those various branches in the
> CVS repository. I lost a little bit the track to the cocoon release
> plans. I did a "cvs status -v someclass" and got this list:
> cocoon_20 (revision: 1.2.2.22)
> -> actual distribution
> cocoon_20_rc2 (revision: 1.2.2.20)
> -> expired or still used?
> cocoon_20_rc1 (revision: 1.2.2.17)
> -> expired or still used?
> cocoon_20_b2 (revision: 1.2.2.6)
> -> actual development?
> cocoon_20_branch_mergepoint (revision: 1.2)
> -> expired or still used?
> cocoon_20_branch (branch: 1.2.2)
> ->expired or still used?
> cocoon_20_b1 (revision: 1.2)
> ->expired or still used?
>
> Could somebody with enough Cocoon karma give me some
> enlightenment, please?!
You're mixing branches and tags. There are only two branches : HEAD and
cocoon_20_branch, all other names are tags that label the various
releases or important points in the project life.
> Cheers
> Gerhard
>
> --------------------------------
> Beam me up... arrgh, no carrier!
> --------------------------------
Personal request : where do all these sentences come form ?
Sylvain
--
Sylvain Wallez
Anyware Technologies - http://www.anyware-tech.com
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Branches and CachingxxxPipline enlightenment request!
Posted by giacomo <gi...@apache.org>.
On Fri, 7 Dec 2001, Gerhard Froehlich wrote:
> Hi,
> I did 2 checkouts:
>
> 1. HEAD:
> The system is using NonCachingxxxPipelines! I've looked into the
> cocoon.xconf but there are the caching ones configured (cocoon.roles
> don't have any Pipline role definition).
>
> 2. cocoon_20
> The system is using CachingxxxPipelines *relief* as configured in the
> cocoon.xconf file and Caching is working and the Store system swaps
> laboriously CachedxxxObjects out to the fs, etc.
>
> I don't understand why the system is using the NonCachingxxxPipelines
> in 1) (seems like Vodoo to me ;) and if there is some higher meaning, why?
>
> The problem is, that this caused some confusion here last days.
> (and this days not only upon me ;-).
>
> A second more personal request are those various branches in the
> CVS repository. I lost a little bit the track to the cocoon release
> plans. I did a "cvs status -v someclass" and got this list:
These aren't branches. They are Tags.
> cocoon_20 (revision: 1.2.2.22)
> -> actual distribution
This is the point where the cocoon_20_branch was tagged cocoon_20 when
Carsten has released it.
> cocoon_20_rc2 (revision: 1.2.2.20)
> -> expired or still used?
Even here cocoon_20_rc2 is a tag not a branch
> cocoon_20_rc1 (revision: 1.2.2.17)
> -> expired or still used?
Same here.
> cocoon_20_b2 (revision: 1.2.2.6)
> -> actual development?
Same here.
> cocoon_20_branch_mergepoint (revision: 1.2)
> -> expired or still used?
Here I've synced the HEAD and the 20 branch and set a tag to indicate
up to which revision mergin has occurred.
> cocoon_20_branch (branch: 1.2.2)
> ->expired or still used?
This is where we actually made the 20 branch from the original HEAD
branch
> cocoon_20_b1 (revision: 1.2)
> ->expired or still used?
This is the tag when we created this CVS repository (out of the one used
for cocoon 1.x)
Hope this helps.
Giacomo
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org