Hi Charlie,

On 7/7/2014 2:42 PM, Charlie Mordant wrote:
Hi Scott,

You're in a right way for sure, I'll try and integrate it :).
Have you tried Cellar?

No, although it looks from scanning the docs as if Cellar could easily be used to implement a new discovery and/or distribution provider...via ECF's transport independent provider architecture. Incidently, we already have an enhancement request to create a discovery provider based upon hazelcast [1].

Let's say that today my stack is AMQ5.9 (JMS 1.1 with STOMP/WebSocketJS powered by JMesnil), CXF3(JaxRS2), Cellar (DOSGI) and Zookeeper to mix all of them.

Ok. We already have a distribution provider implemented on ActiveMQ 5.8 [2]. I believe it would be a simple matter to create distribution providers out of (e.g.) cxf/jax and/or cellar. And we already have a discovery provider based upon zookeeper.

Unfortunately, ECF committers can't currently commit to implementing all desired custom providers, as there are actually too many requests for us to keep up...especially while we are implementing the OSGi R6 additions/changes.

It's one (of several) reasons to provide an open modular architecture and as much documentation as we can...allowing others to easily create/use custom providers without is having to implement all of them.

I'm really interested by 2) as it's not provided by the AC (not for now, but Karaf is not J8 compliant so I doubt completablefuture will be).

I can tell you for sure that 2) works on multiple distribution providers as we auto test/use/example it on both rosgi and ecf generic providers. So a new distribution provider (as described above) would inherit java8/cf behavior completely for free.

Finally, for 3), is it ok for topologies, cluster and enhanced cloud require-capabilities-OBR-powered remote dep management?

I'm not completely sure what you are asking. Since RS/RSA is for remoting/distributing nearly *any* OSGi service, services that have the capabilities you describe (clustering, remote dependency mgmt, etc) would be easily remoted/distributed.

There are other needs for clustering however...e.g. reliable group communication...that may not be a great fit for typical OSGi services. Just for your information, we've done work on a distributed eventadmin implementation also [3].


I'll try it for sure, and make some Itests for your features.

Best regards, and keep up the good work (and the gap filling between this wonderful communities: Eclipse and the Apache one).

Charlie

Thanks,

Scott

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=421239
[2] https://github.com/ECF/JMS
[3] https://wiki.eclipse.org/EIG:Distributed_EventAdmin_Service



2014-07-07 21:47 GMT+02:00 Scott Lewis <[email protected] <mailto:[email protected]>>:

    Hi Folks,

    ECF 3.8.1/Luna is now available for Karaf 3 [1].   This is a
    CT-tested fully-compliant implementation of OSGi R5 Remote
    Services standard [2].   Our implementation only requires OSGi
    v4.3 of the framework, and so will run properly on either Equinox
    or Felix in Karaf 3+.

    In addition to full compliance with OSGi R5 RS/RSA specifications,
    here are some unique features of ECF's impl of RS/RSA:

    1) A transport-independent open architecture.   For remote
    services discovery, open source implementations exist for
    zeroconf, dnssd, zookeeper, and slp, and there are open source
    distribution providers based upon r-osgi, ECF generic/tcp, JMS,
    REST, MQTT, and others. Further, new open or proprietary discovery
    and/or distribution providers are easily created [3], and all
    providers are automatically standards compliant.   Another
    positive aspect to transport independence is that it allows easy
    integration between existing web/rest services and OSGi Remote
    Services.

    2) Support for Java8 CompleteableFuture for asynchronous remote
    services [4]

    3) Immediate support for OSGi R6.  ECF is preparing a release
    (3.9.0) in August 2014 for our CT-tested impl of OSGi R6
    standards. To explain:  The OSGi R6 RS/RSA specifications have not
    been completed by the enterprise experts group (EEG), and so
    release of our R6-compliant impl must wait until the
    specifications and CT are complete.

    Thanks,

    Scott

    [1] https://wiki.eclipse.org/EIG:Install_into_Apache_Karaf
    [2] https://wiki.eclipse.org/ECF#OSGi_Remote_Services
    [3]
    
https://wiki.eclipse.org/Tutorial:_Creating_a_RESTful_Remote_Service_Provider
    [4] https://wiki.eclipse.org/ECF/Asynchronous_Remote_Services
    Project home page: http://www.eclipse.org/ecf




--
Charlie Mordant

Full OSGI/EE stack made with Karaf: https://github.com/OsgiliathEnterprise/net.osgiliath.parent

Reply via email to