commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sven Kuenzler <>
Subject Re: [Morphos] Food for thoughts
Date Sat, 10 Aug 2002 11:02:55 GMT
Nicola Ken Barozzi wrote:


> For example, Cocoon makes a resolver available to Generation Components; 
> personally I think that we must strive to separate as much as possible 
> the location and the generation phases, but we are already doing it... 
> so I guess that it's already ok.
>                <>>>>>><<<<<<<>
> So, it seems we need to remember that we shall never use Resource 
> Locators to our content Morphers, only to the ones that Morph a Location 
> to an actual object.
> This means that the InputSource2SAX Morpher is wrong. We should have an 
> InputSource2StreamMorpher and a Stream2SAXMorpher, so that it's more 
> flexible.
> The point is that we cannot formalize this, because an Object is an 
> Object , we cannot know if it's a resource identifier of some sort, 
> because a computer cannot understand the semantics.
> But if we keep to the simple rule of separating Locators to actual 
> Morphers, we are going to have more flexibility.
> Hey, what about making a Locator interface?
> It could be something like:
>    public void setLocation(Object location);
>    public boolean isLocationReachable();
>    public Object locate();
>    public ObjectFlavor getFlavor();

IIRC, this morpher merge thing came to me when I read about the proposed 
string->file->... chain in Here, the string stage is about 
  converting a file name to a file, right?
So, what impact would the Locator interface on in this scenario? Or is 
this something completely different?


To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message