Christian Schneider created ARIES-1269:
------------------------------------------
Summary: Add blueprint maven plugin
Key: ARIES-1269
URL: https://issues.apache.org/jira/browse/ARIES-1269
Project: Aries
Issue Type: New Feature
Components: Blueprint
Reporter: Christian Schneider
Assignee: Christian Schneider
I have recently created a maven plugin that generates blueprint.xml from CDI,
JEE and Spring annotations.
https://github.com/cschneider/blueprint-maven-plugin
What makes this different from the blueprint annotations support we already got
in aries?
------------------------------------------------------------------------------------------------------------------------
- The blueprint annotations follow the xml style of binding to an exact bean id.
The annotations I used by default bind simply by type which is much simpler to
manage and more in line with Spring @Autowired and CDI @Inject.
Still they also allow to bind by name using @Named
- The aries blueprint annotations are processed at runtime but create xml under
the covers. My plugin on the other hand does all the work at build time.
So at runtime you can install into any existing container running blueprint -
no additional deps needed.
- My plugin uses standard CDI/JEE annotations and where there is no standard
(Services) pax cdi annoations. So people using this style can transition from
and to real CDI quite easily. People with JEE background also feel at home with
this style.
- My plugin also supports some spring annotations like @Autowired, @Component,
@Value. This allows a very fast migration from spring to blueprint. In fact I
used it in a quite big customer project for that case
Sample application
-------------------------
I created an example application that shows how the following features:
- internal wiring
- container managed JPA with transactions
- using and offering OSGi services
https://github.com/cschneider/Karaf-Tutorial/tree/master/tasklist-cdi
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
