Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 55187 invoked from network); 10 Jan 2002 21:32:31 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 10 Jan 2002 21:32:31 -0000 Received: (qmail 26826 invoked by uid 97); 10 Jan 2002 21:32:14 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 26811 invoked by uid 97); 10 Jan 2002 21:32:13 -0000 Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list avalon-dev@jakarta.apache.org Received: (qmail 26789 invoked from network); 10 Jan 2002 21:32:13 -0000 Message-ID: <000901c19a1e$3fc1dad0$701bfbc0@sierrasys.com> From: "Mircea Toma" To: "Avalon Developers List" References: <200201101104.g0AB4p409660@mail012.syd.optusnet.com.au> <3C3DC4B6.80601@yahoo.com> Subject: Re: BlockListener needs more methods Date: Thu, 10 Jan 2002 14:31:55 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: localhost.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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" To: "Avalon Developers List" 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: > For additional commands, e-mail: > -- To unsubscribe, e-mail: For additional commands, e-mail: