Thanks to Andreas and Sagara!

I will give both approaches a try today. I'm very impressed of DA- Launcher. I think this is exactly the thing you want to use. Clean design, easy-to-use and so on... I got it up and running in 5 minutes (would have been 2 minutes if had been using compatible equinox jars to the version of DA-Launcher ;-)).

However, I wonder if there's a way to let DA-Launcher read the bundles from my Eclipse Workspace like Equinox and PDE does it, so that they don't have to be packaged first to run them. If there's no way yet to do it, I still could use DA-Launcher for my distributable later on, which would be great enough, too ;-)

Regards,
        Daniel

Am 19.08.2009 um 10:33 schrieb Sagara Gunathunga:

Just to share my experience , sometimes ago i tested the procedure
mentioned in axis2_osgi_integration.pdf document and  worked with me
without any problem. Also link [1]  describe another approach based on
DA-Launcher.

[1] -  http://www.dynamicjava.org/posts/running-axis2-in-osgi

Thanks ,

On Wed, Aug 19, 2009 at 1:12 PM, Andreas
Veithen<[email protected]> wrote:
Daniel,

Actually I wanted to point you to the following document:

https://svn.apache.org/repos/asf/webservices/axis2/scratch/java/saminda/osgi_test/axis2_osgi_integration.pdf

This has nothing to do with Carbon. Note that I never tested the
approach described in that document myself.

Andreas

On Wed, Aug 19, 2009 at 09:32, Daniel Bimschas<[email protected]> wrote:
Andreas,

thank for you answer. I suppose you wanted to point me to the carbon
framework (http://wso2.org/projects/carbon) mentioned in this thread? It's a nice thing, but for me, it's simply "too much". All I want is a naked Axis2 runtime running in my OSGi container. For my purposes it doesn't make sense to simply introduce another framework as this will produce an even larger distributable with features I don't need and potentially bugs and problems I don't need too, not to mention the time I've to put in to fully understand
what the framework does.

So, I still would be glad to hear about some easy-to-use OSGi compatible
Axis2 distribution.

Kind regards,
       Daniel

Am 10.08.2009 um 19:45 schrieb Andreas Veithen:

Daniel,

Please have a look a the following thread:

http://markmail.org/thread/3xbjzrsvxombqvkd

Andreas

On Mon, Aug 10, 2009 at 18:12, Daniel Bimschas<[email protected]> wrote:

Hi Folks!

I'm trying to simply integrate Axis2 into an Eclipse Equinox OSGi
container.

So far I found no easy way to do that. I think the ideal way is that
there
was a How-To somewhere which says: install file A, B, C, ... from
Axis2-src
distribution and you're done. Is there a tutorial like that which I
missed?
Even more ideal would be an OBR (OSGi bundle repository) repository
holding
the "main" bundle and all it's dependencies, so that one could install it
by
running "obr install" when on Apache Felix or after deploying some OBR
implementation into Equinox.

I tried to other ways to install it, which also failed. First one was
using
an OSGi-Axis2 distribution from the Knopflerfish project which simply
failed
because of invalid bundle headers (syntax errors and missing imports).
Second one was to try to install it after downloading the
src-distribution
of Axis2, running complete build of it with Maven and trying to install
the
individual packages by hand. This is very tedious as there's no easy way
to
find out which bundle/jar imports/exports the packages needed and so on.
Is
there maybe a tutorial for that?

Are there any plans for a Maven target that puts all relevant packages
into
one directory so that OSGi users simply use all jars in it to get up and
running?

I would be very thankful for some help on this (somewhat tedious)
problem!

Kind regards, Daniel



----------------------
Daniel Bimschas
Fleischhauer Straße 45
23552 Lübeck
[email protected]
----------------------






--
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://sagaras.awardspace.com/


----------------------
Daniel Bimschas
Fleischhauer Straße 45
23552 Lübeck
[email protected]
----------------------

Reply via email to