Leo,
>>From: Paul Hammant [mailto:[EMAIL PROTECTED]]
>>
>>Perhaps the point is that like with Pheonix's "Service", it is more of
>>an intellectual interface that a real one.
>>
>
>True. The thing being that not everything is a Component, and that a
>ComponentManager is used to lookup Components and nothing else.
>
>I suggest you define a new interface for AltJB/AltRMI lookup of
>non-Component things. That way, you will be able to extends the interface
>so the lookup is done at a specified host/default host, and so on.
>
>The CM interface only guarantees to give you an object with the same
>interface as the role name - For remote lookup, I want to be able to
>lookup components on a specific server.
>
>You can solve that by extending the role:
>
>manager.lookup ("my.Component/192.168.1.99/NamedComponentInstance")
>
It is done like this....
Object obj = manager.lookup(name);
Where name could be :
"StockPriceFacade" - AltJB handles the lookup, determining where it
is coming from, incl remotely.
"Phoenix:com.tagrum.Jo.JoService" - AltJB routes the call through to
Phoenix's componenet manager. <depends> issues considered.
"AltRMI:SocketObjectStream:abc.com/1234/StockService" - Manual setting
loaction and transport.
>
>but then you
>
>a) modify the CM contract
>b) introduce lots of opportinities for errors.
>
>Compare the above with an interface that's like this:
>
>public interface RemoteObjectManager {
> public Object lookup (String name, URL name);
> public Object lookup (String name, Context context);
>}
>
>or something...
>
Indeed.
- Paul
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
