Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <41D2C997.6050607@apache.org>
Date: Wed, 29 Dec 2004 16:13:27 +0100
From: Carsten Ziegeler <cziegeler@apache.org>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: SourceResolver for custom Source (and SourceFactory)
References: <Pine.OSF.4.61.0412271713260.375568@kosh.hut.fi>
In-Reply-To: <Pine.OSF.4.61.0412271713260.375568@kosh.hut.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Tuomo L wrote:
> Hi,
> 
> I'm writing a custom Source and SourceFactory for Cocoon, which takes 
> uris in this form: mysource:context://foo/bar.zip:mydir/myfile.gif.
> 
> The part between the two ":"'s is a "sub-uri", which I need to resolve. 
> How can I do this, so that any Cocoon URI works, for example: 
> cocoon://foo.bar and html://foo.bar ? The Source stuff seems to be 
> changed lately, so what is the right way to go?
> 
Just implement a SourceFactory with your own Source - you can lookup
the SourceResolver in your implementation and use the resolver to
resolve any Cocoon uri. So in your example above, you have a factory
for your mysource: protocol and inside the factory you use the
resolver to resolve the context: protocol.

There is only one subtle trick with using a resolver inside a
source factory: you can't lookup this component inside the service()
method. If you do so, you end up in an initialization loop.
You have to do a lazy look up of the resolver: the first time you
really need it.

HTH
Carsten