On Friday, November 8, 2002, at 11:55 AM, Peter Donald wrote:
Gotcha. You still need an array of interfaces to proxy by the time you call the Proxy.newInstance method though.. that's what I was getting at :)On Sat, 9 Nov 2002 03:41, Peter Royal wrote:I wasn't ;)On Friday, November 8, 2002, at 11:41 AM, Peter Donald wrote:That works, but I'd like to be able to pass in an array of interfaces
to the ComponentFactory then to tell the ComponentProxyGenerator what
to proxy for.
Where do I get this array of interefaces from?Good question :) How were you going to handle this?
I was basically going to proxy every interface that could reasonably
considered a potential Work interface. The main reason being that Fortress
does not know about exposed services as such - hence we add em all in by
default. Maybe too generous but in theory it should not break backwards
compat (unless people cast to an implementation).
-pete
--
peter royal -> [EMAIL PROTECTED]
--
To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
