Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <33537.80.219.8.172.1099699843.squirrel@80.219.8.172>
In-Reply-To: <418C02CB.2000307@mm.st>
References: <418C02CB.2000307@mm.st>
Date: Fri, 5 Nov 2004 18:10:43 -0600 (CST)
Subject: Re: Getting a return value from a cocoon:// source
From: "Antonio Gallardo" <agallardo@agssa.net>
To: dev@cocoon.apache.org
User-Agent: SquirrelMail/1.4.3a-1
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal

Hi Steven:

What about a Session Attribute? Is this a solution? Can you explain more
whta are you trying to do and maybe we can findanother solution. ;-)

Best regards,

Antonio Gallardo

Steve Krulewitz dijo:
> (I just sent this to the user list but Tim suggested I send it here as
> well)
>
> Hey all --
>
> I have a situation where I have a generator calling a cocoon:// source,
> and I would like to be able to return a value to the calling pipeline.
> My current solution is for the called pipeline to put this value into
> the returned xml, and I then have a transformer that just scans through
> the xml looking for that particular element.  However, this is very slow
> when there is a lot of xml returned.
>
> I've tried setting things into the request context from the called
> pipeline, but the caller can never read it.  Is there a trick to getting
> the caller's request context in the called pipeline?
>
> If all else fails, is ThreadLocal a possibility?
>
> thanks,
> -steve
>