Thanks for the reply. Only one question about the last point (please see below)
Stephen McConnell <[EMAIL PROTECTED]> wrote: Milind Tendulkar wrote: >Hi, > >We have developed a server application that we intend to put in phoenix container. It >has 3 compoenets - a jar (server side), a web module (under tomcat) and xindice (as >XML repository). > >As we learned about phoenix: >1. A block has to be a java class not & an interface. >2. A service has to be an interface. >3. The block has to implement the interface. >4. The block can provide a service to the outside world thro' the interface. > >Now we face some questions and need advise: >1. Does the block has to be runnable? > No. The Avalon lifecycle for the equivalent of the Runnable interface is Startable - but this is only an interface in which the container invokes start and stop - the implementation is responsible for setting up its own thread of execution. >2. How do we make application (jar) runnable? Do we write a wrapper class or we >implement the RMI in a sort of wrapper. > Just create a new thread inside you implementation class and in the Startable.start() method you start you thread and return. >3. How will the client be accessing application? Just by instatiating it? Or is an >RMI >communication necessary? > Depends who you mean by the client. If the client is abother component/block then the container will take care of providing a reference to the service to all consuming components. If the client is a user - then its implementation specific - you could be access a service via the web - RMI, IIOP, whatever. > >Actually we want container to instantiate an object of application (using initialize >method) and then serve client requests. Application has one execute method that >clients must call. > >Can anyone advise on this? > > Sounds to me like you want a component that is going to invoke execute on a component following a HTTP request. Presumable the regust will contain info about the componet to activate. If thats correct - you should take a look in the archive for messages dealing with the avalon-jetty component. The application will listen on RMI or IIOP(as suggested). But web module must instantiate tomcat from within container and communicate with XML repository xindice. Now xindice itself is a server listening on specific port. Will this be an issue? We're looking at using web module like: http://localhost:port/module. Cheers, Steve. > >Thanks in advance. > > > >--------------------------------- >Do you Yahoo!? >Protect your identity with Yahoo! Mail AddressGuard > > -- Stephen J. McConnell mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------- Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard
