Hi Christian,
Well the initial version of the RI is effectively done, though we need
some process in the OSGi expert group to play out before putting it in
Apache. So we don't have a release firm date as such, but we are eager
to get it out there for exactly the reasons you've stated.
We also have an external dependency on some extensions to the OSGi
platform to allow us to intercept OSGi service registry lookups. This
enables triggering the creation of the CXF proxy on the client side,
without any impact on the application code. Which is kinda neat.
Since support for these service registry hooks isn't there yet in the
main OSGi platforms, we prototyped it up in a fork of Apache Felix in
order to get started quickly. However, we expect a reference
implementation of these hooks to be available soon in Equinox.
What OSGi platform are you targeting? (i.e. Equinox, Felix, Knopflerfish
....)
Thanks for your offer of help with testing etc. Our test coverage
definitely will need some beefing up, and there'll also be a TCK coming
down the road at some point. On the implementation side, there'll be
some work involved in implementing recent changes to the spec and also
extending support for enabling different CXF QoS via the distributed
OSGi abstraction layer (currently we support reliability, addressing,
decoupled, logging, & SOAP 1.1/1.2, but we'd like to extend this to
include some security-related QoS and multiple transports).
Cheers,
Eoghan
Christian Schneider wrote:
Hi Eoghan,
this sounds very interesting. I will start with the bundles from the cxf
distro. Do you have any release date already set for the dOSGI
implementation? I think the sooner people start to work with it the
sooner it will become stable. I would be willing to help with testing
and even with the implementation as this is exactly what we would have
to do ourselves anyway.
Best regards
Christian
Eoghan Glynn schrieb:
Hi Christian,
Rather than bundlizing each individual module, the CXF build instead
creates one big aggregate bundle containing everything.
Well actually it creates two bundles, as Sergey recently enhanced it
to also build a smaller-footprint bundle which is more focused on the
happy path of web service enablement (e.g. it excludes the CORBA
binding, javascript frontend, codegen tooling and some other
bits'n'bobs).
Look under <cxf>/distribution/bundle for details of how the bundles
are built.
Your idea around exposing OSGi services as a CXF web service sounds
very similar to what Sergey & I did with the reference implementation
of distributed OSGi. The spec for dOSGi (RFC 119) is currently being
finalized by the OSGi Enterprise Expert Group - once adopted and
released to the public domain (hopefully in the next few weeks), we'll
be contributing our CXF-based RI to Apache.
So we could save you some work :)
Your thinking about a centralized registry may be covered by the OSGi
Discovery Service, which is also being standardized as part of RFC
119. Another group has just started on a reference implementation of
this piece.
Cheers,
Eoghan
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
