Merlin2 Extension architecture

[Raj Saini]

Hi,

Merlin2 provides pluggable lifestyle extensions. Components can declare a dependency on a lifecycle extension provide. Components can also be provider of lifecycle extension service.

The Eclipse IDE (www.eclipse.org) provides the same kind of mechanism where the plugs can declare hook to extension points of other plugs or they can also declare their own extensions. The Merlin2 extension architecture seems similar to the Eclipse extension architecture. In Eclipse IDE it is possible to extend the IDE functionality by writing the plugins.

What is the purpose of the extension architecture in Merlin2? Is it possible to write a core application and extend the functionality by writing pluggable blocks? I am impressed by the Eclipse plugin architecture. Eclipse allows tool venders to write tools and plug them to the base IDE. Does Merlin2 extension architecture server the same purpose for server application

Extending the server application by writing self-contained plugs (or components) would be a nice feature. Though Phoenix offers this facility but it is on server level. In my opinion a server developer need deployable components (or plugs) for the server instead of many deployable servers application in a single kernel.

Thanks,


Raj Saini



--
To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>