karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré ...@nanthrax.net>
Subject Re: [DISCUSSION] Karaf Boot
Date Thu, 10 Sep 2015 16:42:30 GMT
Why not, as soon as we provide a valid default configuration in 

I'm afraid that this approach is still too low level/technical. The 
purpose of karaf-boot is to be "key turn": just inherit from the pom, 
use annotation: bang it's done.


On 09/10/2015 06:38 PM, Christian Schneider wrote:
> The idea is of course to only add the really needed namespaces and
> elements.
> The newest version should provide that. I think we will need to create a
> kind of plugin layer in the maven-blueprint-plugin. So
> people can create plugins to support their custom namespaces and
> annotations.
> This might then be a good hook for karaf if you still want the special
> annotations. The big benefit of using the maven bundle plugin instead of
> creating a completely new plugin is that
> you can leverage several technologies together. So for example you could
> add a plugin to discover rest services and auto create the blueprint
> based on the cxf namespace.
> If you create a completely new maven plugin then you have to find a way
> to make sure the different technologies work together. This is a lot of
> effort even if it looks simple add the start.
> So I propose we work together on the maven-blueprint-plugin instead and
> make sure it also covers your cases.
> About targeting different frameworks on the output side I am not sure if
> it can be done. CDI like blueprint is a bit more static while DS is much
> more dynamic. On the other hand DS does not support interceptors.
> So I do not think you can map the same annotations to DS and blueprint
> at the same time without loosing a lot of functionality.
> Christian
> Am 10.09.2015 um 18:19 schrieb Jean-Baptiste Onofré:
>> I know. The plugin is a bit invasive: it add it even if you don't use
>> persistence and transaction annotations ;)
>> And again, it's generic and abstracted annotations on top of it.
>> Today we generate blueprint, maybe tomorrow spring, maybe tomorrow DS,
>> but generic level.
>> Regards
>> JB

Jean-Baptiste Onofré
Talend - http://www.talend.com

View raw message