You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-user@ws.apache.org by mvnjacky <di...@d-velop.de> on 2008/03/18 14:00:50 UTC
Ready to run environment
Hello *,
i am trying to get a minimum OSGI environment based on eclipse equinox to
work.
I am statrting the osgi environment using this command:
call java -jar org.eclipse.osgi.core.jar -console -clean
The osgi frameworks starts an almost all bundles get activated.
But i am not able to get the muse bundle to work.
osgi> ss
Framework is launched.
id State Bundle
0 ACTIVE org.eclipse.osgi_3.3.1.R33x_v20070828
1 ACTIVE javax.specs.jar
2 ACTIVE org.apache.felix.scr_1.0.0
3 ACTIVE org.eclipse.equinox.log_1.0.100.v20070226
5 ACTIVE org.eclipse.osgi.services_3.1.200.v20070605
6 ACTIVE org.eclipse.equinox.http.jetty_1.0.1.R33x_v20070816
7 ACTIVE org.eclipse.equinox.http.servlet_1.0.1.R33x_v20070816
8 ACTIVE org.mortbay.jetty_5.1.11.v200706111724
9 ACTIVE org.eclipse.equinox.common_3.3.0.v20070426
10 ACTIVE org.apache.commons.logging_1.0.4.v200706111724
11 ACTIVE org.apache.xerces_2.8.0.v200705301630
12 ACTIVE org.apache.xml.resolver_1.1.0.v200705310020
13 INSTALLED org.apache.muse.complete_2.2.0
osgi>
When i try to start the muse bundle i get a missing constraint:
org.osgi.framework.BundleException: The bundle could not be resolved.
Reason: Missing Constraint: Import-Package: org.apache.xpath;
Anyone got a ready to run runtime based on osgi for muse or any kind of
axis2?
Or does anynone know which bundles are required to get it to work?
regards, dieter
--
View this message in context: http://www.nabble.com/Ready-to-run-environment-tp16120690p16120690.html
Sent from the Muse User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
RE: Ready to run environment
Posted by mvnjacky <di...@d-velop.de>.
Just for info,
i found a first way to get the Axis2 Servlet running within the osgi
framework.
I just created a Folder in the directory "src/main/resources". This
automatically
gets includes into the bundle by using the maven-bundle-plugin.
That folder contains a subfolder called WEB-INF and this contains another
subfolder called "lib" which includes (at first) all axis2 libs. After that
i set the
OSGi Bundle Classpath for each lib, like WEB-INF/lib/activation-1.1.jar.
Furthormore
it is necessary to add the path for the Axis2 modules. Modules like the
"addressing-1.3.mar"
or "axis2-scripting-1.3.mar". For all modules i created another folder under
"src/main/resources"
named "modules". Finally i added another directory to the OSGi Bundle
Classpath wich contains
the log property files (commons-logging.properties, log4j.properties). IT IS
IMPORTANT TO SET
THE CLASSPATH TO THE FOLDER CONTAINING THOSE PROPERTY FILES. OTHERWISE NO
LOGGING.
No i am able to use the RegisterServlet method to register the Axis2 Servlet
within the
OSGi HTTP Service (based on jetty).
<!--
******************************************************************* -->
<!-- BUILD
-->
<!--
******************************************************************* -->
<build>
<plugins>
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<version>1.0.0</version>
<extensions>true</extensions>
<configuration>
<instructions>
<Import-Package>
!.,
*;resolution:=optional
</Import-Package>
<Export-Package>
org.apache.axis2.*
</Export-Package>
<!--
Private-Package>com.dvelop.esb.runtime.service.soap.axis2.*</Private-Package-->
<Bundle-ClassPath>
.,
WEB-INF/classes,
WEB-INF/modules,
WEB-INF/lib/activation-1.1.jar,
WEB-INF/lib/annogen-0.1.0.jar,
WEB-INF/lib/axiom-api-1.2.5.jar,
WEB-INF/lib/axiom-dom-1.2.5.jar,
WEB-INF/lib/axiom-impl-1.2.5.jar,
WEB-INF/lib/axis2-adb-1.3.jar,
WEB-INF/lib/axis2-adb-codegen-1.3.jar,
WEB-INF/lib/axis2-ant-plugin-1.3.jar,
WEB-INF/lib/axis2-clustering-1.3.jar,
WEB-INF/lib/axis2-codegen-1.3.jar,
WEB-INF/lib/axis2-fastinfoset-1.3.jar,
WEB-INF/lib/axis2-java2wsdl-1.3.jar,
WEB-INF/lib/axis2-jaxbri-1.3.jar,
WEB-INF/lib/axis2-jaxws-1.3.jar,
WEB-INF/lib/axis2-jaxws-api-1.3.jar,
WEB-INF/lib/axis2-jibx-1.3.jar,
WEB-INF/lib/axis2-json-1.3.jar,
WEB-INF/lib/axis2-jws-api-1.3.jar,
WEB-INF/lib/axis2-kernel-1.3.jar,
WEB-INF/lib/axis2-metadata-1.3.jar,
WEB-INF/lib/axis2-mtompolicy-1.3.jar,
WEB-INF/lib/axis2-saaj-1.3.jar,
WEB-INF/lib/axis2-saaj-api-1.3.jar,
WEB-INF/lib/axis2-spring-1.3.jar,
WEB-INF/lib/axis2-xmlbeans-1.3.jar,
WEB-INF/lib/backport-util-concurrent-2.2.jar,
WEB-INF/lib/commons-codec-1.3.jar,
WEB-INF/lib/commons-fileupload-1.1.1.jar,
WEB-INF/lib/commons-httpclient-3.0.1.jar,
WEB-INF/lib/commons-io-1.2.jar,
WEB-INF/lib/commons-logging-1.1.jar,
WEB-INF/lib/geronimo-annotation_1.0_spec-1.1.jar,
WEB-INF/lib/geronimo-jms_1.1_spec-1.1.jar,
WEB-INF/lib/httpcore-4.0-alpha5.jar,
WEB-INF/lib/httpcore-nio-4.0-alpha5.jar,
WEB-INF/lib/httpcore-niossl-4.0-alpha5.jar,
WEB-INF/lib/jalopy-1.5rc3.jar,
WEB-INF/lib/jaxb-api-2.0.jar,
WEB-INF/lib/jaxb-impl-2.0.5.jar,
WEB-INF/lib/jaxb-xjc-2.0.5.jar,
WEB-INF/lib/jaxen-1.1.1.jar,
WEB-INF/lib/jettison-1.0-RC1.jar,
WEB-INF/lib/jibx-bind-1.1.5.jar,
WEB-INF/lib/jibx-run-1.1.5.jar,
WEB-INF/lib/juli-6.0.10.jar,
WEB-INF/lib/log4j-1.2.14.jar,
WEB-INF/lib/mail-1.4.jar,
WEB-INF/lib/mex-impl-1.3.jar,
WEB-INF/lib/neethi-2.0.2.jar,
WEB-INF/lib/soapmonitor-1.3.jar,
WEB-INF/lib/stax-api-1.0.1.jar,
WEB-INF/lib/tribes-6.0.10.jar,
WEB-INF/lib/woden-1.0-incubating-M7b.jar,
WEB-INF/lib/wsdl4j-1.6.2.jar,
WEB-INF/lib/wstx-asl-3.2.1.jar,
WEB-INF/lib/xalan-2.7.0.jar,
WEB-INF/lib/xbean-2.2.0.jar,
WEB-INF/lib/xercesImpl-2.8.1.jar,
WEB-INF/lib/xml-apis-1.3.03.jar,
WEB-INF/lib/XmlSchema-1.3.2.jar
</Bundle-ClassPath>
</instructions>
</configuration>
</plugin>
</plugins>
</build>
--
View this message in context: http://www.nabble.com/Ready-to-run-environment-tp16120690p16396265.html
Sent from the Muse User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
RE: Ready to run environment
Posted by le...@bt.com.
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:dieter.schulten@d-velop.de]
Sent: 19 March 2008 10:35
To: muse-user@ws.apache.org
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: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
Re: Ready to run environment
Posted by mvnjacky <di...@d-velop.de>.
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: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org