On Wednesday 17 December 2003 17:30, [EMAIL PROTECTED] wrote: > >>Hi, > >> > >>I'm building an app-server around rpc calls, I decided to use the > >>avalon framework and merlin, and the fulcrum-xmlrpc and apache-xmlrpc > >>stuff. However, I've run into a slight problem. > > > > So do I. > > Me too ;) > > I'd like to know how far you've come with your respective implementations, > as I seems to be in the same situation.
This seem to be a commonality. IIUIC, you guys want to expose Avalon services running in Merlin as XML-RPC and/or SOAP services. At the moment there is no "nice way" to do this, but you "could" use the "not stable" LifeCycle Extension mechanism. But be aware, it is still not finalized and expected to change some more. There is also a security aspect that needs to be addressed. As for the plans, we are currently trying to stablize Merlin into a releasable state, as a Christmas present. Ease-of-use, such as 'running-out-of-the-box' and similar issues are currently being addressed. There after, there are a whole series of issues that we wish to address. Here is some of "my concerns", I am sure Stephen has other wishes on his list; * Security - JAAS leveraged user/role/rights system, with pluggable user/role/rights management systems. * Stablize the Life Cycle Extension mechanism. * JMX - Automatic creation of MBeans for installed components. * Service Listeners - similar to Phoenix. * Interception - a system to intercept method calls to services. * Service Availability Contract - Where components are allowed to "be available", "not available". This is required to allow truly dynamic and distributed systems (in the long-run Clustered Merlin servers). Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
