Hi Jean-Baptiste
Could you clarify what do you understand to be content of the Enterprise
Features subproject? I understand this project should contain the
feature xml files. But it should also contain additional components
beaing part of the enterprise features (like the bundle with Activiti
configuration or the KarafEE extensions). Is it ok?
Regards
Krzysztof
On 08.02.2014 23:58, Jean-Baptiste Onofré wrote:
Hi,
Yes, it's what I proposed some time ago: extract the non-core features
from Karaf itself (and not ship them with the distributions), and
provide it as a dedicated sub-project.
I will move forward on this with a formal proposal and branch on github.
Regards
JB
On 02/08/2014 11:56 PM, Krzysztof Sobkowiak wrote:
Hi Jean-Baptiste
As long as ServiceMix is not going to die the bundles and specs can be
still part of ServiceMix (until another good place for them will be
found). It makes perhaps no sense to move them into Karaf.
I can remember one discussion somewhere on the mailing list about
extracting the Karaf enterprise features in a separate subproject. This
subproject could contain the current enterprise and spring features
from Karaf, the features providing the routing, messaging and services
functionality (by referencing the proper well defined versions of Camel,
CXF and ActiveMQ and providing the missing functionalities like the
connection factory as described in previous mail), the Activiti
integration and many other interesting enterprise features like Karafee.
The features repositories could be referenced in Karaf and included in
Karaf distribution. It is important that the features should by up to
date and installable in the new Karaf releases and not stay some
releases back. I'd like take for example the latest Karaf 3.x release
(or even snapshot) and make an esb solution installing some features (as
described in my previous mail).
Yeah, ServiceMix 5+ could still exist as an assembly containing the esb
features from Karaf Features subproject. If we had esb features which
are always up to date with Karaf we could just install them on Karaf or
build a new ServiceMix based on a new Karaf version. I tried to upgrade
SMX 5 to Karaf 2.3.3 and the integration tests started to fail
occasionally, but the distribution was stable (I think it's rather a
problem with the Scala tests than the upgraded SMX)
The old ServiceMix features like JBI should still live in ServiceMix.
But I think the features will be not included in ServiceMix 5 and later.
Best regards
Krzysztof
On 08.02.2014 22:56, Jean-Baptiste Onofré wrote:
Hi Krzysztof,
A couple of years ago, I remember a discussion with Guillaume (at
ApacheCon, Vancouver, around a couple of beers ;)), where we dealt
about doing likely what you said in ServiceMix (ServiceMix acting as a
features container). It's why we started to think about something like
Cave (as a Karaf Enterprise Features Repository).
I think your idea is interesting, and it's what I aim for Karaf Cave.
I mean, now, it's not very efficient to have non-core features
"embedded" in Karaf: it's not easy for users to update to new feature
versions without updating to a new Karaf version.
I think that non-core features should be maintained and available
outside of Karaf container itself.
We can see the following Karaf sub-projects:
- Karaf (it's what we have now, the container)
- Bundles (it's the ServiceMix Bundles "moved" as Karaf subproject)
- Features (it's the non-core features, like enterprises, activiti,
etc)
- Cellar
- Cave
- EIK
- WebCosnole
Now, regarding the bundles, as it's not directly related to Karaf
(it's more OSGi generic), I wonder if it makes sense to have it in
Karaf. I did a proposal in the past to do it at Felix. Mayben we can
imagine to have a Pax project for the bundles.
For now, I would leave the bundles in ServiceMix.
ServiceMix could still provide:
- bundles and specs
- NMR layer
- a assembly leveraging and gathering features
--
Krzysztof Sobkowiak
JEE & OSS Architect | Technical Architect @ Capgemini
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
e-mail: [email protected] <mailto:[email protected]> |
Twitter: @KSobkowiak
