Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 51729 invoked from network); 4 Feb 2004 22:31:07 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 4 Feb 2004 22:31:07 -0000 Received: (qmail 65345 invoked by uid 500); 4 Feb 2004 22:30:44 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 65285 invoked by uid 500); 4 Feb 2004 22:30:44 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 65194 invoked from network); 4 Feb 2004 22:30:43 -0000 Received: from unknown (HELO fep03-svc.swip.net) (130.244.199.131) by daedalus.apache.org with SMTP; 4 Feb 2004 22:30:43 -0000 Received: from apache.org ([80.170.241.39]) by fep03-svc.swip.net with ESMTP id <20040204223048.EHSI2492.fep03-svc.swip.net@apache.org> for ; Wed, 4 Feb 2004 23:30:48 +0100 Message-ID: <40217298.3050206@apache.org> Date: Wed, 04 Feb 2004 23:30:48 +0100 From: Sylvain Wallez User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: fr, en, en-us MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: cvs commit: cocoon-2.1/src/blocks/fop/java/org/apache/cocoon/serialization FOPSerializer.java References: <20040204143958.22614.qmail@minotaur.apache.org> <40213A5A.8070508@gmx.de> <40215846.4050309@reverycodes.com> In-Reply-To: <40215846.4050309@reverycodes.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Vadim Gritsenko wrote: > Joerg Heinicke wrote: > >> Does this mean we can now reference images using all Cocoon >> protocols? I mean also for and similar? >> >> On 04.02.2004 15:39, sylvain@apache.org wrote: >> >>> sylvain 2004/02/04 06:39:58 >>> >>> Modified: src/blocks/fop/java/org/apache/cocoon/serialization >>> FOPSerializer.java >>> Log: >>> Add support for all cocoon protocols for >> xlink:href="..."/> >> >> ... >> >>> + SourceProtocolHandler.setup(this.resolver); >> >> >> >> And this by only such a simple change? Woah!! This would be worth a >> mentioning in status.xml, Sylvain, as this solves frequently asked >> questions on FOP/Batik. > > > > I still wonder how this will fork in multithreading environment... > This is static method call, and each sitemap have different resolver. > Will this crash on 2 simulteneous requests? This uses a ThreadLocal under the hood, so there should be no problem. This trick is necessary because Batik's URL resolving mechanism doesn't allow to pass the SourceResolver along the call chain. Sylvain -- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } Orixo, the opensource XML business alliance - http://www.orixo.com