To put this in context, Hollow proxies are a bit like mixins
except they redirect invocations on an interface.

e.g. the proxy implements javax.sql.DataSource which is redirected to
javax.resource.spi.ConnectionManager.allocateConnection()
There is no object that actually implements DataSource.

I don't know whether it is worth making this a first class construct in AOP
(i.e. configurable in xml) rather than having to write a redirecting interceptor to do this?

Some of the use cases can be complicated/domain specific.

e.g. in the DataSource case, the redirect actually does

public Object invoke(Invocation invoke) throws Throwable
{
 ConnectionRequestInfo cri = makeCRIFromArgs(invocation);
 ManagedConnectionFactory mcf = getFromInstanceMetaData(invocation);
 return connectionManager.allocationConnection(mcf, cri);
}

"kabir.khan@jboss.com" wrote:

This is until I figure out what you mean by the rest of your post :-)