Mircea,
It is a good idea. However RMI forces RemoteException to be specified
on all methods and the the interface in question to extends Remote.
Here is Fede's Repository as is :
public interface Repository extends Component {
Repository getChildRepository( String childName );
}
Here is is if you want it to be compatible with RMI :
public interface Repository extends Component, Remote{
Repository getChildRepository( String childName ) throws
RemoteException;
}
Are we going to add RemoteException to all methods that we might want to
transport?
Sorry for being facetious, but I really dislike RemoteException. That
after a long association.
To give your question a serious answer, the API you propose as a general
one could delegate to AltRMI and Glue (only one impl of SOAP). I can't
vouch for the others.
Regards,
- Paul H
>Hi Paul,
>
>How about having a publishing service interface. This way you can have
>blocks implementing different publishing schemes. JMX, RMI, SOAP, JNDI, Jini
>(I would love this one), and AltRMI ;) are all good candidates to integrate
>Avalon with other technologies. I think it makes sense to have publishing
>service instead of a component because usually you publish object just for
>another framework within an application.
>
>The interface would be very similar with the one from SystemManager in
>Phoenix:
>
>public interface PublishingService
>{
> void register( Object name, Object object, Class[] interfaces )
> throws PublishingException, IllegalArgumentException;
>
> void register( Object name, Object object )
> throws ManagerException, IllegalArgumentException;
>
> void unregister( Object name )
> throws ManagerException;
>}
>
>for different schemes, name Object can be :
>
>JMX -> ObjectName
>SOAP -> relative URL
>JNDI -> String
>Jini -> ServiceItem
>AltRMI -> String
>
>
>What do you think?
>
>Mircea
>
>
>
>----- Original Message -----
>From: "Paul Hammant" <[EMAIL PROTECTED]>
>To: "Avalon Developers List" <[EMAIL PROTECTED]>
>Sent: Thursday, January 10, 2002 9:43 AM
>Subject: Re: BlockListener needs more methods
>
>
>>Peter,
>>
>>>>so that I wait for a block coming up I need and then
>>>>just keep the block-object. Then I just have to invoke the requested
>>>>methods, that's it. Very simpel and it works perfectly.
>>>>
>>>thats how it is designed to work.
>>>
>>For the AutoPublisher I am working there could be many of the services
>>that might want to by published through one service ("AltrmiPublisher").
>> As they could come in any order, some fair amount of storage in Vectors
>>would be required.
>>
>>It might be nice if there were a method called 'void allBlocksAdded()'
>>so that all that storing I had done could be used easily.
>>
>>I'd vote for Loggable too by the way.
>>
>>Regards,
>>
>>- Paul H
>>
>>
>>--
>>To unsubscribe, e-mail:
>>
><mailto:[EMAIL PROTECTED]>
>
>>For additional commands, e-mail:
>>
><mailto:[EMAIL PROTECTED]>
>
>
>
>--
>To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
