forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r376653 - /forrest/events/forrest-friday/20060210-log.txt
Date Fri, 10 Feb 2006 13:00:07 GMT
Author: crossley
Date: Fri Feb 10 05:00:05 2006
New Revision: 376653

URL: http://svn.apache.org/viewcvs?rev=376653&view=rev
Log:
Update

Modified:
    forrest/events/forrest-friday/20060210-log.txt

Modified: forrest/events/forrest-friday/20060210-log.txt
URL: http://svn.apache.org/viewcvs/forrest/events/forrest-friday/20060210-log.txt?rev=376653&r1=376652&r2=376653&view=diff
==============================================================================
--- forrest/events/forrest-friday/20060210-log.txt (original)
+++ forrest/events/forrest-friday/20060210-log.txt Fri Feb 10 05:00:05 2006
@@ -350,3 +350,88 @@
 [23:39] tscherler: :)
 [23:39] tscherler: gracias
 [23:39] _Gav_: themes.core does not create themes directory in target site, will this change
+[23:40] tscherler: ø? incompatible encoding
+[23:40] tscherler: _Gav_ can you explain what u mean?
+[23:40] _Gav_: \forrest\whiteboard\plugins\org.ap​ache.forrest.themes.core\themes\
+[23:41] _Gav_: has all the pelt.fv etc and common.fv and all contracts
+[23:41] _Gav_: these are not recreated in a seed-sample
+[23:41] _Gav_: hmm, maybe thats why
+[23:42] tscherler: no
+[23:42] _Gav_: need a new target, seed-rc1
+[23:42] tscherler: hmm
+[23:42] tscherler: or we need to update all seeds and add
+[23:42] _Gav_: otherwise manual copying of themes from ../themes.core is neccessary
+[23:42] tscherler: resource/themes
+[23:42] tscherler: no
+[23:43] tscherler: in a project you only override the original
+[23:43] twilliams_: sorry thorsten you've lost me.  how/why would an input module extend
a pipeline component?
+[23:43] tscherler: you do not need contract in your project
+[23:43] tscherler: twilliams_
+[23:44] _Gav_: ok, so where does project.theme=pelt get contracts from?
+[23:44] tscherler: do not understand the question
+[23:44] tscherler: ah
+[23:44] tscherler: now I gues
+[23:44] tscherler: ok the pipe concepts sets some params
+[23:44] tscherler: that forces cocoon to ommit the cache
+[23:45] tscherler: now since it is a java class you can set the caching in the lm class via
such a class, right?
+[23:45] tscherler: makes sense?
+[23:45] tscherler: (13:44:01) _Gav_: ok, so where does project.theme=pelt get contracts from?
+[23:45] tscherler: see the fallback mechanism
+[23:46] tscherler: moment 
+[23:46] twilliams_: your just suggesting that the lm caching respect the context of the pipe
that it's in (e.g. caching/non-caching)?
+[23:47] tscherler: yes
+[23:47] twilliams_: i thought you were suggesting actually change the LM Module to extend
from Pipeline component and I wasn't getting why/how
+[23:47] twilliams_: Now that i understand what you're suggesting...
+[23:47] tscherler: no would be too much trouble ;-)
+[23:48] twilliams_: lm's can be referenced in different pipes indepedently, so i'm still
not sure how that would work in reality
+[23:48] tscherler: _Gav_http://svn.apache.org/viewcvs.cgi​/forrest/trunk/whiteboard/plugins/​org.apache.forrest.plugin.internal​.dispatcher/src/java/org/apache/fo​rrest/dispatcher/acting/RecursiveD​irectoryTraversalAction.java?view=​markup
+[23:48] _Gav_: I understand the fallback of themes, and over-riding them in new themes, but
if no themes directory exists in site structure..
+[23:48] tscherler: http://svn.apache.org/viewcvs.cgi/​forrest/trunk/whiteboard/plugins/o​rg.apache.forrest.plugin.internal.​dispatcher/locationmap.xml?view=ma​rkup
+[23:49] _Gav_: does it then fallback to pelt skin?
+[23:49] tscherler: skin
+[23:49] tscherler: no skins are dead in rc1
+[23:50] tscherler: _Gav_ we are talking about contracts right?
+[23:50] _Gav_: yep
+[23:50] _Gav_: say I have a new seed-sample, it is created without a /resources/themes/*
folder
+[23:50] twilliams_: in other words would lead to some indeterminate caching because of multiple
references to the same hints
+[23:51] _Gav_: Tim, were keeping Thorsten busy
+[23:51] _Gav_: :)
+[23:51] tscherler: <!-- Project implementation of templates have priority before default
ones.         If no implementation can be found we use the noFt (~ - no forrest:template)
implementation.          {1} name of the contract -->     
+[23:51] tscherler: see below this _Gav_ it is in the dispatcher lm
+[23:51] tscherler: jeje
+[23:52] tscherler: (13:50:39) twilliams_: in other words would lead to some indeterminate
caching because of multiple references to the same hints -> hmm I am not sure because I
have to admit that I have not looked close enough into the classes
+[23:52] tscherler: but
+[23:52] _Gav_: so what would a noFT site look like - looks like a pelt site to me
+[23:52] tscherler: I think it will set a cocoon enviroment variable in the objectmodel
+[23:52] tscherler: or another place
+[23:52] twilliams_: _Gav_: Tim, were keeping Thorsten busy
+[23:53] twilliams_: and he thought he was going to have another peaceful FF
+[23:53] tscherler: that you can get in your class (somthing like: super.getCachingStatus)

+[23:53] tscherler: jeje
+[23:53] twilliams_: yeah i don't doubt i can get the name of the pipe
+[23:53] _Gav_: maybe I'll just get on with converting the theme and understand this bit later
+[23:54] twilliams_: pipeA is caching / pipeB is non-caching
+[23:54] tscherler: (13:52:34) _Gav_: so what would a noFT site look like - looks like a pelt
site to me -> site? You mean contract.
+[23:54] twilliams_: pipeA refers to lm:my.resource and also pipeB refers to lm:my.resource
+[23:54] tscherler: the " If no implementation can be found we use the noFt (~ - no forrest:template)
implementation"
+[23:55] tscherler: is used as fallback that the whole process is not failing if the requested
contract is not found
+[23:55] tscherler: it is resulting in nothing
+[23:55] _Gav_: I did a forrest run on a seed-sample site that had no themes directory, and
looked like pelt
+[23:56] tscherler: twilliams_  put can't you get the type of the pipe?
+[23:56] tscherler: better name
+[23:56] tscherler: no type was right:
+[23:56] tscherler: <map:pipeline type="caching" internal-only="true">
+[23:57] tscherler: yeah
+[23:57] tscherler: _Gav_ because you activated pelt theme
+[23:57] tscherler: since it is not in your project we are using the plugin core contracts
for pelt
+[23:57] twilliams_: type= is a friendly (e.g. user-determined name) right?
+[23:58] tscherler: ø? incompatible encoding
+[23:58] tscherler: no
+[23:58] _Gav_: hmm, how do you copy a quote in IRC
+[23:58] tscherler: You define it in the component configuration
+[23:58] tscherler: <map:pipe name="caching" src="org.apache.cocoon.components​.pipeline.impl.CachingProcessingPi​peline"/>
+[23:59] tscherler: but yeah it is user defined
+[23:59] twilliams_: so i'd hate to depend on that in an input module
+[23:59] tscherler: on the naming you mean
+[23:59] twilliams_: and i don't see as where the pipes implement some caching interface either
+[23:59] twilliams_: right



Mime
View raw message