Re: [Proposition] - Apache KarafEE

[Charles Moulliard <cm...@gmail.com>]

To keep you informed, here are the last news :

- Discussion with Apache Geronimo team is ongoing
(http://apache-geronimo.328035.n3.nabble.com/Proposition-Collaboration-between-Karaf-Geronimo-td3588113.html#a3591838)
and as they are interested to move from GBeans to something much more OSGI
compliant, then collaboration between teams is open.
- Apache OpenEJB team has created a Apache KarafEE (project). Till now, it
is part of OpenEJB subversion trunk
(http://svn.apache.org/repos/asf/openejb/trunk/openejb/osgi/) and contains
Karaf 2.2.4 + rebrand + command to list, deploy, undeploy EJBs components
and of course OpenEJB deployed as features
- Apache KarafEE or Karaf + OpenEJB have succeeded to deploy @Stateless,
@Statefull, @Singletion, @Inject beans like also @Entity beans (which are
deploy by OpenEJB in OpenJPA)
- The beans can be called using OSGI service and interface name or using EJB
lookup mechanism (local, remote)
- Different tests have been made like also calling EJBs beans from camel
routes 

--
View this message in context: http://karaf.922171.n3.nabble.com/Proposition-Apache-KarafEE-tp3585332p3631670.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.

Re: [Proposition] - Apache KarafEE

[Charles Moulliard <cm...@gmail.com>]

Perhaps with KarafEE, we have established a new era for Java OSGI
Application Servers design like Apache Tomcat more than a decade ago

On Wed, Jan 4, 2012 at 1:46 PM, Ioannis Canellos <io...@gmail.com> wrote:

> Reading all these interesting views I come to realize that so far all app
> servers that use OSGi, actually ported their existing codebase into OSGi
> leaving a "gap", since they were not originally designed for that job.
>
> What I find really exciting is the fact that this is the only approach I am
> aware of, that goes the other way around (building EE features on top of
> OSGi).
>
> I am really curious to see how it will evolve.
>
> Really interesting stuff.
>
> --
> *Ioannis Canellos*
> *
> FuseSource <http://fusesource.com>
>
> **
> Blog: http://iocanel.blogspot.com
> **
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> Apache Camel <http://camel.apache.org/> Committer
> Apache ServiceMix <http://servicemix.apache.org/>  Committer
> Apache Gora <http://incubator.apache.org/gora/> Committer
> Apache DirectMemory <http://incubator.apache.org/directmemory/> Committer
> *
>

Re: [Proposition] - Apache KarafEE

[Ioannis Canellos <io...@gmail.com>]

Reading all these interesting views I come to realize that so far all app
servers that use OSGi, actually ported their existing codebase into OSGi
leaving a "gap", since they were not originally designed for that job.

What I find really exciting is the fact that this is the only approach I am
aware of, that goes the other way around (building EE features on top of
OSGi).

I am really curious to see how it will evolve.

Really interesting stuff.

-- 
*Ioannis Canellos*
*
FuseSource <http://fusesource.com>

**
Blog: http://iocanel.blogspot.com
**
Apache Karaf <http://karaf.apache.org/> Committer & PMC
Apache Camel <http://camel.apache.org/> Committer
Apache ServiceMix <http://servicemix.apache.org/>  Committer
Apache Gora <http://incubator.apache.org/gora/> Committer
Apache DirectMemory <http://incubator.apache.org/directmemory/> Committer
*