Melih,
Sorry for the delay in answering your
question. My implementation is similar to that found in the Knoplerfish
distribution – I have a servlet that overrides
the AxisServlet, and I deploy it using a servlet context I create based on some header information
provide by bundles using the Axis service (my way of faking multiple webapps). I step on the Axis MSG and RPC providers to
replace them with OSGi-specific extensions so that I
can take care of class loading issues. I load the Axis services (WSDD files)
relative to the bundle (using the Bundle.getEntryPaths
method), which sounds different from your approach. My current implementation has the Axis
jar stuffed into a Muse-specific bundle – I’m currently refactoring this so that someone who doesn’t need
WSRF/WSDM could use the Axis bundle standalone. What’s your time frame
for needing a SOAP stack in equinox? Do you need this running in the bridged servlet environment, or with the internal HTTP service? If
bridging, would you prefer to bridge at the Axis layer or at the HTTP layer?
Jeff, looks like I’ll
be doing the same paperwork dance for Muse. Any idea of the ETA for that new streamlined
process? J
Cheers,
Joel
-----Original Message-----
From:
equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Melih Onvural
Sent: Wednesday, June 07, 2006
12:05 PM
To: Equinox development mailing
list
Subject: Re: [equinox-dev] Axis in
OSGi on Equinox
Joel,
We're trying to use Axis as a translator between the data we receive from some
web forms passed through SOAP into XDS query languages on
the backend. We keep running into the problem where it can't name our service.
The baffling this is the same processes (we're just going through
AxisServlet) work fine under the /axis folder but give null service name errors
under the /bridge folder. Did you run into this at all? What was your
general approach to creating a bundle with Axis?
Jeff,
I didn't realize that that was the situation. I'll ask my manager to clarify
the situtation for me, and will let you know the result. Thanks for letting me
know.
Thanks to all,
Melih Onvural
melih.onvural@xxxxxxxxx
On 6/7/06, Hawkins, Joel <Joel.Hawkins@xxxxxxxxxxxxx>
wrote:
Sure. The new version of
Muse (currently being contributed by IBM) implements an 'IsolationLayer'
interface to abstract the SOAP provider from the Muse core. Currently there are
two implementations that are going into the code line – one for Axis 1.X
and one for Axis 2.X. The work I'm doing repackages the Muse core as a set of
bundles, adds 'bundle awareness', and allows the actual implementation of the
SOAP provider to be late-bound as an OSGi service. The Axis IsolationLayer
implementations are packaged as bundles and connect to the core through the
afore-mentioned service interface. http://wiki.eclipse.org/index.php/Corona_Design_SOA
has a diagram. At present, the SOAP provider interface is fairly limited
(Muse/WSDM make light demands on the underlying SOAP container), basically
providing implementation details (name, version) and access to the underlying
engine. For the Corona implementation, I've added the capability to publish
POJOs as a stop-gap on my way to integrating with Tuscany/SCA.
All of this work is
intended to be donated to the Muse project, although I've tried to structure
the code in such a way that I can add additional capabilities as we consume
Muse's OSGi implementation in Corona . Can you give me some idea of how you'd
like to use Axis? It would help me fill in the SOAP provider details.
Subject: Re: [equinox-dev] Axis in OSGi on Equinox
Melih, Just to be clear you can use a wide range of software in Eclipse
projects but you have to be sure to go through the Eclipse Contribution
process. Even if some other Eclipse project is using a third party
library like Axis, a project like yours (I seem to recall that you are working
on an Eclipse project) would have to request permission to include Axis in your
deliverables. We are working on processes and mechanisms to make this
all easier and more transparent but for now this is what you have to do.
Note that this is true as well if you want to use the Knopflerfish
bundling of Axis. That is, it is not a technological issue but rather a
legal and process issue.
Joel,
can you say more about what Muse is doing with bundlized versions of Axis?
Jeff
Joel,
Thanks for the heads up. I had found the Knoplerfish example, but wasn't sure
that I could use it. It's good to know that this has been
done, and I will search in the Corona project to see how it was accomplished,
and hopefully be able to emulate it. Thanks for the
reply.
Melih
On 6/6/06, Hawkins, Joel <Joel.Hawkins@xxxxxxxxxxxxx
> wrote:
Melih ,
I've done this for the
Corona project (Axis 1.3 – Axis 2 is still in the works), and will submit
the code as part of the Apache Muse project as soon as Muse's administrative
kinks are ironed out.
The folks at Knoplerfish (http://www.knopflerfish.org/ ) have an Axis plugin for OSGi as well (Axis 1.x, OSGi R3).
Cheers,
Joel Hawkins
-----Original Message-----
From: equinox-dev-bounces@xxxxxxxxxxx [mailto: equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Melih Onvural
Sent: Tuesday, June 06, 2006 4:51 PM
To: Equinox development mailing list
Subject: [equinox-dev] Axis in OSGi on Equinox
Group,
Has there been any push to install Axis as a servlet in OSGi? I read in the
newsgroup mention of developed
plugins that might one day make their way down the pipeline into the OSGi
layer, but I haven't found any
mention since. If this hasn't been done yet, where would be a good place to
start investigating as this is something
I'd like to add? Thanks,
Melih Onvural
melih.onvural@xxxxxxxxx
=00The contents of this e-mail are intended for the named addressee only. It contains
information that may be confidential. Unless you are the named addressee or an
authorized designee, you may not copy or use it, or disclose it to anyone else.
If you received it in error please notify us immediately and then destroy it.
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
=00The contents of this
e-mail are intended for the named addressee only. It contains information that
may be confidential. Unless you are the named addressee or an authorized
designee, you may not copy or use it, or disclose it to anyone else. If you received
it in error please notify us immediately and then destroy it.
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
=00The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. |
