Hi guys,
As I'm going to upgrade Osgiliath framework to the latest an greatest Karaf
version, I'm re-synchronizing features version (e.g. aligning jta versions
to have one and only one javax.transaction package exported with only one
version if possible).
I made this thread with some todos, some interrogations, etc...
Generic questions:
* Is aries-jpa 2 dry? production ready, etc... Christian, I heard you'll
join/be a recognized contributor of a new company with some awesome guys:
will you stay to be active on this project (community), or better, will you
'sell' these wonderful things at these guys, which are using technologies
that are not as mature/different (some guys in the Eclipse community will
greet you, and the one who are not aware of this will ask how they did
before you).
* Are Deltaspike-web and maybe Agorava soon be OSGi ready? IMO CDI is a
very nice spec and OSGI should throw their good old injection stuff to move
to one way of doing things (throwing blueprint, scr, direct whiteboard
interaction, etc), also social things are more and more mandatory to launch
a website...
* Is Karaf easily adaptable to 'standard' remote dependency management
(OBR), so is it easy to launch a Karaf fully featured server within BND (it
brings some nice stuff: repository setup and semantic versioning scan).
* I'll love to see a Require-Capabilty='osgiEE-web' and setting up a fully
fledged Karaf ^^. In a first time, we could remove feature dependencies
using capabilities and resolving it).
* Deltaspike/CDI can be transactional, listen config from configadmin,
deltaspike-data can also be tx aware, it could be nice to dig in it.
* Should I use Hibernate? I want JPA 2.1, search engine, auditing... I'd
love to use Apache stuff, but...
* Will Apache community (also OPS4J one <3) will consume some 'generic'
poms: standardizing latest versions of the servlet/injection/jta spec,
etc... There are many frameworks 'Karaf aware' (cxf, amq, pax-*), it could
be nice to avoid concurrent versions of 'spec' stuff. Maven pom fragments
could help if available (at lest, osgiliath, with some help can be a
missing part of this issue, ensuring all these different project are
interoperable)
* Why isn't the Eclipse community using pom-first, bnd, etc to create and
release their product: it should be an objective to have one way of doing
things (and throwing Tycho, P2, extension point and stuff). This community
is already OSGI ready, they're just making the wrong choices and should be
mentored.
* Without the Apache 'MegaPom' in place A simple jar with a main method
could 'unpack' a feature to give standard pom informations and
variabilizing tha feature.
e.g.
<feature name="stuff" version="1.0.0">
<bundle>mvn:bargroup/barartifact/2.0.0</>
</feature>
=>
<feature name="stuff" version="${stuff.version}">
<bundle>mvn:bargroup/barartifact/${bargourp_barartifact.version}</>
</feature>
<dependencyManagement>
<dependency>
<groupId>bargroup</groupId>
<artifactId>bargroup</artifactId>
<version>${bargroup_barartifact.version}</version>
</dependency>
</dependencyManagement>
<dependencies>
<dependency>
<groupId>bargroup</groupId>
<artifactId> barartifact </artifactId>
</dependency>
</dependencies>
<properties>
<bargroup_barartifact.version>2.0.0</bargroup_barartifact.version>
<stuff.version>1.0.0</stuff.version>
</properties>
* When will you drive the OSGI community! IMO Karaf is the most advanced
OSGi framework (or the most respectful and simply the best) of all time.
About the issues (for now):
* On pax-cdi:
Issues:
I'm using the 1.0.0.RC1 version, 'pax-cdi-1.2-web' is using 'pax-cdi-1.2'
feature, which is inexistant: this feature should be removed.
I'll continue on this thread posting some minor issues that migration, feel
free to merge contributions in your respective projects and improving the
bests technologies of all times!
Best regards,
--
Charlie Mordant
Full OSGI/EE stack made with Karaf:
https://github.com/OsgiliathEnterprise/net.osgiliath.parent
