Gotcha. Thanks for the clarification. I'll go check out the Axis-
Users lists.
-c
On Nov 5, 2009, at 9:27 PM, Daniel Kulp wrote:
On Thu November 5 2009 9:21:18 pm Christopher Blunck wrote:
Thanks for the followup, Dan. I'll look within the Axis community
for
answers.
I posted to CXF because of the "Distributed OSGi" feature. Can
anyone
confirm that the "Distributed OSGi" feature relies on Axis/Axis2
under
the covers to provide SOAP messaging between separate OSGi containers
and the services deployed within them? If so then that gives me hope
that using Axis/Axis2 from within OSGi is technically possible and it
also tells me that I can look at CXF as a possible example on how to
accomplish it...
No, the Distributed OSGi feature relies on CXF under the covers to
provide
SOAP messaging between separate OSGi containers and the services
deployed
within them. :-) No Axis2 involved.
Dan
-c
On Nov 5, 2009, at 9:15 PM, Daniel Kulp wrote:
CXF is COMPLETELY separate from Axis and Axis2. While Axis2 and
CXF share
some libraries (like wss4j, neethi, etc..), the underlying SOAP
processing are
completely different code bases.
I PERSONALLY recommend migrating the applications to CXF, but I can
definitely
understand why that's not an option. But you would need to post
this to the
Axis2 lists. The WSO2 folks could probably help you as they've
done a lot
of osgi stuff with Axis2 for their products.
Dan
On Thu November 5 2009 3:36:51 pm Chris Blunck wrote:
Hello-
I have some code that relies on an Axis generated client to call a
SOAP web
service. I'm interested in migrating that client to an OSGi
bundle. I
thought this would be a pretty trivial process but I've become
entangled in
OSGi's dependency management and packages.
I'm working with Felix 2.0.1 and Axis2 (although this happens with
Axis1 as
well).
I'm posing this question to the CXF community because the
"Distributed
OSGi" section of the CXF website advertises:
It implements RFC 119 using Web Services, leveraging SOAP over HTTP
and
exposing the Service over a WSDL contract. Starting from 1.1-
SNAPSHOT, Java
interfaces can also be exposed and consumed as RESTful JAX-RS
services.
From my preliminary reading it appears as though CXF allows
services to
call one another using SOAP as a transport. Given how embedded
Axis is
with the rest of the CXF project my instinct tells me that the
Distributed
OSGi folks have used Axis as their SOAP client and server
implementation.
The problems I've hit with Axis and Felix is that I can't bundle up
all the
dependent JARs and put together an Import-Package statement that
will
actually work and allow the client classes in my bundle to use Axis
properly.
Given that the CXF folks have presumably done this I'm very
interested in
understanding their approach and how they accomplished rolling up
Axis into
an OSGi bundle that can be used from within Felix.
PS - I'm using Maven (including the bundle plugin, which just calls
bnd).
My apologies if this was sent to the incorrect list.
-c
--
Daniel Kulp
[email protected]
http://www.dankulp.com/blog
