coliver 2003/04/12 17:34:44
Modified:src/scratchpad/src/org/apache/cocoon/transformation
JexlTransformer.java
Log:
recycle variables
Revision ChangesPath
1.7 +2 -1
cocoon-2.1/src/scratchpad/src/org/apache/cocoon/transformation/JexlTrans
coliver 2003/04/12 17:24:46
Modified:src/scratchpad/src/org/apache/cocoon/transformation
JXPathTransformer.java JexlTransformer.java
Log:
added and tags to JXPathTransformer and JexlTransformer: these can
only be used to create local aliases of existing obj
coliver 2003/04/12 16:35:30
Modified:src/scratchpad/src/org/apache/cocoon/transformation
JXPathTransformer.java JexlTransformer.java
Log:
added object model objects: request, response, session, context to JXPath and Jexl
contexts: so these are now consistent
I've incorporated Albert's patch (with slight modifications for backward
compatibility) into FlowVelocityGenerator in the scratchpad. This should
also make it backward-compatible with the current Velocity generator. If
the flowscript objects aren't present, then it behaves as before - but
with
coliver 2003/04/12 14:29:05
Modified:src/scratchpad/src/org/apache/cocoon/generation
FlowVelocityGenerator.java
Log:
Incorporated patch from Albert Kwong and attempted to make backward-compatible with
VelocityGenerator
Revision ChangesPath
1.4
Stefano Mazzocchi wrote:
I've taken a pretty serious look at XQuery and I think that it fits the
needs for what I wanted. Ivelin wrote a pretty nice article on it for
xml.com, you might want to check it out.
+1, with a warning: XQuery is not supposed to react on an incoming data
feed but to "pull
Stefano Mazzocchi dijo:
> on 4/12/03 5:03 PM Geoff Howard wrote:
>
>
>> I'd be for it - but what about bugs marked blocking 2.1 release? And
>> what about pending major changes to central contracts (flow)?
>> How do we avoid getting stalled in beta?
>
> by releasing early and often, fixing one iss
Stefano Mazzocchi dijo:
> a) they get a release we consider stable in code (in fact cocoon
> 2.1-dev is pretty damn rock solid from a code point of view, I never had
> a failure in months and many are using it in production with no
> problems)
>
> What do you think?
I think there are just one imp
