commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Colebourne" <>
Subject Re: [PATCH] AdaptorRegistry
Date Tue, 11 Mar 2003 23:24:41 GMT

I've taken a look at adaptor registry, and I'm currently not entirely
convinced. Its not that it doesn't work, or that its probably very useful.

The problem I see is that it is basically a lookup class, searching for
something mapped using an interface and class as a key. Which is fine, unles
I want to use something else as a key as well, or do the lookup slightly
differently. (eg. the lookup mechanism I have at work uses an interface,
enumerated type, call stack and method arguments to decide on the
implementation to pick).

So I guess its perhaps my view that maybe each 'framework application' has
its own lookup mechanism, and this is Tapestrys and that its too 'religious'
for [lang]. Or am I just being narrow minded?


----- Original Message -----
From: "Howard M. Lewis Ship" <>
To: <>
Sent: Thursday, March 06, 2003 10:16 PM
Subject: [PATCH] AdaptorRegistry

A while back, I discussed the AdaptorRegistry used throughout Tapestry.

Think of it as a "smart Map", that connects arbitrary objects to a
"best-fit" adaptor by doing a search based on inheritance and implemented

I've created a patch from the jakarta-commons/lang/src.

This patch adds the org.apache.commons.lang.util.AdaptorRegistry (torn out
of Tapestry), plus a test suite.

I've run the entire commons-lang test suite succesfully.

Please get back to me if you decide to add this to commons-lang.  I think it
is a good fit.

Howard M. Lewis Ship
Creator, Tapestry: Java Web Components


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

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

View raw message