This probably needs to be a community driven effort. A "product in its
own right" actually triggers an armada of jboss/redhat folks to do
additional work on top of what we put out as a community project. This
would only be done if justified by sufficient interest.
A good starting point would be to modify the build such that is supports
configurable subsystems. From a modular service container perspective
it's probably worth to stick with the standards and use the osgi only
profile.
On 09/03/2012 09:48 PM, Olaf Bergner wrote:
While I think that JBoss AS 7's architecture and implementation
are
outstanding neither I nor the company I'm working for have a need for a
JEE container. What we *do* have a need for, though, is a robust,
performant, flexibel and manageable runtime for deploying our networked
services in. Having taken a look at JBoss AS 7's Modular Service
Container, its extension mechanism, its flexibel configuration model and
the fact that it's based on JBoss Modules I started to think that a
JBoss AS 7 distribution stripped down to its core just might fit the bill.
Beyond creating that minimal distribution itself I think all it would
take is to add some documentation, especially on how to use the Modular
Service Container, something I couldn't find *any* documentation for.
Plus maybe a sample application or two. Provided someone in the know
volunteered to assist me I would be more than willing to provide those.
What do you think?
Regards,
Olaf
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx