<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000'>This is a great topic, but it might be a couple of weeks premature.<br><br>During the FY'14 kickoff meetings in NewCastle, we will be discussing this topic, from the idea of having a core/base that all products, including EAP would be layered on top of.<br><br>I am responsible for presenting this basic idea, and have done some work already on understanding what I think that core or base infrastructure would look like.<br><br>Having said that, my general idea is that the base or core infrastructure would consist of the MSC/and domain components (along with others) that form the basis of a runtime and a management layer, with one management and configuration API. Everything else would layer on top of that, and share the same management layer below.<br><br>Andy<br><br><hr id="zwchr"><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Thomas Diesler" <thomas.diesler@jboss.com><br><b>To: </b>"Brian Stansberry" <brian.stansberry@redhat.com>, "Guillaume Nodet" <gnodet@redhat.com><br><b>Cc: </b>"jboss-as7-dev@lists.jboss.org Development" <jboss-as7-dev@lists.jboss.org>, osgi-wrk-grp@redhat.com<br><b>Sent: </b>Friday, March 8, 2013 9:21:33 AM<br><b>Subject: </b>[jboss-as7-dev] Configuration/management functionality AS/Fuse<br><br>Hi Brian/Guillaume,<div><br></div><div>in the OSGi Working Group kick-off meeting I proposed a line of thought does goes like this:</div><div><br></div><div><div><ul class="MailOutline"><li><i>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. </i></li><li><i>For long term consolidation of the two product lines (i.e. EAP & Fuse) there are two functional areas key: management and configuration</i></li><li><i>There should be one way to configure the various subsystems that run on the platform</i></li><li><i>There should be one API for managing the platform</i></li><li><i>The consolidation effort could initially focus on these two areas and aim to elliminate </i><i>functional overlap and conflicts</i></li></ul><div><i><br></i></div></div><div>In parallel to the general <a href="https://docspace.corp.redhat.com/docs/DOC-135571" target="_blank">requirement gathering</a> I'd like to start a conversation about the respective <i>management/configuration </i>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. </div><div><br></div><div><ul class="MailOutline"><li>How are Fuse products configured?</li><li>How does AS unified configuration work?</li></ul><div><br></div></div><div>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.</div><div><br></div><div>What do you think?</div><div><br></div><div>cheers</div><div>--thomas</div><div>
<div><pre class="moz-signature">xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx </pre><div><br></div></div><br class="Apple-interchange-newline">
</div>
<br></div><br>_______________________________________________<br>jboss-as7-dev mailing list<br>jboss-as7-dev@lists.jboss.org<br>https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</blockquote><br></div></body></html>