Hi Dieter I'm sorry I can't bring you any good news from our implementation of the Muse framework, but I do think you deserve an answer even though it might be as beneficial as you would have liked.
I can't say that I remember much regarding people talking about using the osgi way, most people seem to be using the Axis or mini options given with Muse. I myself have taken to use the mini option and just ant scripting my way through the process of generating a framework based on a WSDL and RMD file approach, then copying in business logic in a compile step and then deploy the whole batch directly into an Apache deployment. So basically I'm "just" using the Eclipse framework as a nice GUI for typing my business logic. That said have you had a look at the MUSE MARC? Perhaps there's some stored answers to your question. /Lenni -----Original Message----- From: mvnjacky [mailto:[EMAIL PROTECTED] Sent: 19 March 2008 10:35 To: [email protected] Subject: Re: Ready to run environment We are using the maven-bundle-plugin to build our own osgi bundles and we use the maven-dependency-plugin to automatically build a osgi runtime containing all our bundles. This way we can use maven to manage all our bundles and we can use a kind of "OneClick" distribution generation. This autoamtic generation process creates all configured jar files (bundles), the proper configuration file (configuration/config.ini) and a batch file to start the osgi basesd server application. Now we would like to use axis2 in our osgi based server and the best way to get an Axis2-OSGi-Service running would be a bunch of osgi like bundles, so we can just add a few entries to our configuration file to manage the automatic build process. If we need another osgi based bundle (maven bundle packaging) we just put an entry like this to our build.xml file. <artifactItem> <groupId>org.eclipse.osgi</groupId> <artifactId>osgi-core</artifactId> <version>3.3.1.R33</version> <overWrite>true</overWrite> <outputDirectory>${dist}</outputDirectory> <destFileName>org.eclipse.osgi.core.jar</destFileName </artifactItem> The way we build OSGi bundles gives us the ability to use our bundles within Apache Felix, Eclipse Equinox, Knopflerfish and so on. Just like the meaning of OSGi to create reusable service components. "Service" in the sense of an "OSGi Service" (one service specification as java interfaces and multiple, posibble service implementations). Is nobody else using this kind of build process to build OSGi based applications and OSGi based services? I am talking about applications without any GUI, just "OSGi Server Application". And are there no ready to use maven artifacts to build an osgi bases Axis2 server? regards, dieter -- View this message in context: http://www.nabble.com/Ready-to-run-environment-tp16120690p16142683.html Sent from the Muse User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
