Hi Brian/Guillaume,
in the OSGi Working Group kick-off meeting I proposed a line of thought does goes like
this:
AS can be seen as an R5 compliant Core Framework that can be bootstrapped like any other
compliant framework. We can take proper behaviour of the OSGi API layer for granted and
can therefore safely assume that the Core Framework that Karaf currently runs on (i.e.
Felix) can be replaced by AS.
For long term consolidation of the two product lines (i.e. EAP & Fuse) there are two
functional areas key: management and configuration
There should be one way to configure the various subsystems that run on the platform
There should be one API for managing the platform
The consolidation effort could initially focus on these two areas and aim to elliminate
functional overlap and conflicts
In parallel to the general requirement gathering I'd like to start a conversation
about the respective management/configuration functionality in the two product lines and
initially identify the overlap/conflicts. Perhaps we could start with the easier of the
two (i.e. configuration) and hear from each other how this currently works.
How are Fuse products configured?
How does AS unified configuration work?
The goal would be to come up with a specific set of requirements for the target platform
that accommodates the configuration needs for both product lines. We could then have a
simmilar approach for the management layer.
What do you think?
cheers
--thomas
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx