Reinhard Poetz wrote:
> Carsten Ziegeler wrote:
>> Reinhard Poetz schrieb:
>>
>>> Carsten Ziegeler wrote:
>>>
>>>
Ok, so let's change the strategy and fix the standalone service
selector... :) If svn works again I can do this on monday evening - if
noone beats me to it.
>>>
>>> I did
Reinhard Poetz wrote:
>
> Right, but that's easily fixed (see
> http://people.apache.org/~reinhard/ProcessingNodeBuilderFactory.java). I
> would
> prefer getting rid of the StandaloneServiceSelector as it is everything else
> than a simple class for a simple task and why do all those builders
Carsten Ziegeler wrote:
Reinhard Poetz schrieb:
Carsten Ziegeler wrote:
Ok, so let's change the strategy and fix the standalone service
selector... :) If svn works again I can do this on monday evening - if
noone beats me to it.
I didn't fix the StandaloneServiceSelector but replaced it wi
Reinhard Poetz schrieb:
> Carsten Ziegeler wrote:
>
>> Ok, so let's change the strategy and fix the standalone service
>> selector... :) If svn works again I can do this on monday evening - if
>> noone beats me to it.
>
> I didn't fix the StandaloneServiceSelector but replaced it with a factory.
Giacomo Pati wrote
> Doesn't get me any further. Still getting
>
> java.lang.NullPointerException
> at
> org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(CallFunctionNode.java:113)
>
> Any additional ideas?
>
Yes :) The model is not evaluated in the selector. If
Carsten Ziegeler wrote:
Ok, so let's change the strategy and fix the standalone service
selector... :) If svn works again I can do this on monday evening - if
noone beats me to it.
I didn't fix the StandaloneServiceSelector but replaced it with a factory.
Basically the factory works for me an
On Fri, 12 May 2006, Reinhard Poetz wrote:
Date: Fri, 12 May 2006 17:57:46 +0200
From: Reinhard Poetz <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: CallFunctionNode problems in trunk
Giacomo Pati wrote:
-BEGIN PGP SIGNED MESSAGE-
Giacomo Pati wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've something working for an app I'm migrating to cocoon-2.2. Could one
of the other bug hunters check if the attached patch works for her,
too? If so that patch could be a base for how to solve this issue.
It works for . I
!
Giacomo
On Fri, 12 May 2006, Giacomo Pati wrote:
Date: Fri, 12 May 2006 16:56:28 +0200 (CEST)
From: Giacomo Pati <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: CallFunctionNode problems in t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 12 May 2006, Carsten Ziegeler wrote:
Date: Fri, 12 May 2006 16:23:58 +0200
From: Carsten Ziegeler <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: CallFunctionNode problems in trunk
Giacom
Giacomo Pati schrieb:
> On Fri, 12 May 2006, Carsten Ziegeler wrote:
>
>>> Date: Fri, 12 May 2006 16:05:16 +0200
>>> From: Carsten Ziegeler <[EMAIL PROTECTED]>
>>> Reply-To: [email protected]
>>> To: [email protected]
>>> Subject
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 12 May 2006, Carsten Ziegeler wrote:
Date: Fri, 12 May 2006 16:05:16 +0200
From: Carsten Ziegeler <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: CallFunctionNode problems in trunk
Reinhard
Reinhard Poetz wrote:
> Carsten Ziegeler wrote:
>> Giacomo Pati schrieb:
>>
>>> I'm hunting that bug too ;-)
>>>
>>> My observation until now is that:
>>>
>>> a) SitemapLanguage#createNodeBuilder creates the CallNodeBuilder
>>> b) it seems (during my debugging) there is only one CallNodeBuilder in
Carsten Ziegeler wrote:
Giacomo Pati schrieb:
I'm hunting that bug too ;-)
My observation until now is that:
a) SitemapLanguage#createNodeBuilder creates the CallNodeBuilder
b) it seems (during my debugging) there is only one CallNodeBuilder in
the system (even though it is not marked Thre
Reinhard Poetz schrieb:
> Carsten Ziegeler wrote:
>> Ignore my last email - the current code is correct. The singleton
>> variable is set to false some lines below :(
>
> Just wanted to answer that it doesn't fix it. IIUC the container with the
> builders is setup in SitemapLanguage.java#405-430.
Giacomo Pati wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm hunting that bug too ;-)
My observation until now is that:
a) SitemapLanguage#createNodeBuilder creates the CallNodeBuilder
b) it seems (during my debugging) there is only one CallNodeBuilder in
the system (even though i
Giacomo Pati schrieb:
>
> I'm hunting that bug too ;-)
>
> My observation until now is that:
>
> a) SitemapLanguage#createNodeBuilder creates the CallNodeBuilder
> b) it seems (during my debugging) there is only one CallNodeBuilder in
> the system (even though it is not marked ThreadSafe as
Carsten Ziegeler wrote:
Ignore my last email - the current code is correct. The singleton
variable is set to false some lines below :(
Just wanted to answer that it doesn't fix it. IIUC the container with the
builders is setup in SitemapLanguage.java#405-430. But I don't understand how
the se
Ignore my last email - the current code is correct. The singleton
variable is set to false some lines below :(
Carsten
Carsten Ziegeler wrote:
> Yes, this could be the problem. I briefly looked through the code and
> (i'm not sure) it seems that avalon components without a lifecycle
> interface (
@cocoon.apache.org
Subject: CallFunctionNode problems in trunk
I'm not sure if I'm on the right track. What I found so far is that if a node
is a LinkedProcessingNodeBuilder its linkNode() method is called. When the
tree processor is set up, a node builder is registered for this step by
adding
Reinhard Poetz schrieb:
> I'm not sure if I'm on the right track. What I found so far is that if a node
> is
> a LinkedProcessingNodeBuilder its linkNode() method is called. When the tree
> processor is set up, a node builder is registered for this step by adding it
> to
> the linkedBuilders c
I'm not sure if I'm on the right track. What I found so far is that if a node is
a LinkedProcessingNodeBuilder its linkNode() method is called. When the tree
processor is set up, a node builder is registered for this step by adding it to
the linkedBuilders collection:
public ProcessingNo
22 matches
Mail list logo
