You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "John E. Conlon" <jc...@verticon.com> on 2006/11/21 22:15:27 UTC
[OSGi] Status - Commons and Mina Support
As part of the ongoing effort to update support for OSGi ApacheDS and
Mina I have committed several OSGi projects to the sandbox/jconlon.
These projects provide:
all the need pieces for OSGi Mina
and lay the initial foundations for a full featured OSGi ADS backend
that I will be committing next week.
Please check out these projects, build them and try them out in an OSGi
runtime and let me know what you think. If you have questions I will do
my best to answer them.
If you have not worked with OSGi previously and want to get started
goto:
http://incubator.apache.org/felix/ and read the documentation, download
sources, and build.
(Have tested the committed projects within the felix and equinox OSGi
runtimes.)
1. osgi-commons projects
Both ADS and Mina depend on third party libraries. To offer ADS and
Mina OSGi support these libraries must also support OSGi and be
installed and their packages exported on the OSGi runtime. To facilitate
this support (in an interim basis until the Felix commons project is
initiated or the libraries are made available by their authors as osgi
bundles) within the sandbox/jconlon/osgi-commons directory you will find
simple pom based projects for creating annotated jars (aka OSGi bundles)
for
antlr, commons-collections, commons-lang, and jzlib.
Note on the maven Plugin:
These projects utilize the new org.apache.felix maven-bundle-plugin to
do the wrapping/annotating of the jars. This plugin offers some unique
features over the first generation maven-osgi-plugin so if you have used
the Enrique's original plugin this one will take a little time getting
used to.
To build all the commons projects:
cd sandbox/jconlon/osgi-commons
mvn clean install
2. osgi-services
a, logging-service
Support for an OSGi ApacheDS and Mina will require the slf4j logging
packages to be made available on the OSGi runtime. Unfortunately since
not all library authors have adopted slf4j, some like Spring-OSGi
require commons-logging. So in order to provide the logging packages
that we and our likely functional collaborators will need -
Within the sandbox/jconlon/osgi-services/logging-service directory you
will find an OSGi Bundle offering an implementation of the OSGi
LogService, library support for Apache slf4j, and slf4j support for
Apache commons-logging. All services are based on the slf4j simple
implementation.
Configuring logging in an OSGi runtime:
To change the logging configuration from the defaults, create/edit the
configuration properties in the <osgiruntimeWorkingDir>/
conf/log4j.properties file, then stop and restart the bundle.
b. logging-service-integration-test
This is the OSGi integration-test project for logging-service. This
project builds a OSGi environment, loads various bundles, and tests the
logging-service is doing it's thing. It is strictly optional and will
require downloading and building of the Spring-OSGi sources.
http://www.springframework.org/osgi
3. osgi-mina
a. integration-osgi
The pom based project in sandbox/jconlon/osgi-mina/integration-osgi is
an OSGi annotated jar/bundle for Mina as requested in
http://issues.apache.org/jira/browse/DIRMINA-27
For it to resolve in an OSGi it will require the following packages to
be exported in the runtime:
com.jcraft.jzlib (see #1. above)
org.slf4j, (see #2.a above)
org.springframework.beans.factory,
org.springframework.beans.factory.config,
org.springframework.core.io,
org.springframework.util
The springframework packages bundled for OSGi are provided in the Spring
OSGi sub project: http://www.springframework.org/osgi
b. mina-osgi-example
The sandbox/jconlon/osgi-mina/mina-osgi-example is an example of a mina
osgi server application. Based on the mina chat example this
application utilizes Spring-OSGi. The beauty of Spring-OSGi (available
in spring 2.1) is that with it we can create our beans and provide the
wiring without any dependencies on OSGi or for that matter Spring. Cool
eh?
Project also includes a spring-container server client testcase.
c. mina-osgi-example-integration-test
This is the OSGi integration-test project for mina-osgi-example. It is
strictly optional and will require downloading and building of the
Spring-OSGi sources at http://www.springframework.org/osgi to get it to
build and run.
How does it work?
This project builds an OSGi environment, loads Spring-OSGi and bundles
required by Mina and the mina-osgi-example and then starts the mina-
osgi-example. The Spring-OSGi will detect the start of the mina-osgi-
example and find its spring configuration, wire the beans and start the
server. The testcase will bring up a chat client and bounce some
messages at it.
feedback, comments?
John
Re: [OSGi] Status - Commons and Mina Support
Posted by "John E. Conlon" <jc...@verticon.com>.
Heads up. Code resides in the apacheds sandbox right now, but will move
mina related projects to the mina sandbox by end of week.
cheers,
John
On Wed, 2006-11-29 at 18:56 -0800, Enrique Rodriguez wrote:
> On 11/21/06, John E. Conlon <jc...@verticon.com> wrote:
> > As part of the ongoing effort to update support for OSGi ApacheDS and
> > Mina I have committed several OSGi projects to the sandbox/jconlon.
> ...
>
> This looks like great work! I just took some time to catch up on
> Spring-OSGi integration and there certainly is a lot happening there.
> I will fire up your code shortly. Some of the resources I read
> through were:
>
> Spring OSGi support gaining momentum
> http://blog.interface21.com/main/2006/09/07/spring-osgi-support-gaining-momentum/
>
> OSGi and Spring
> http://www.osgi.org/blog/2006/08/osgi-and-spring_29.html
>
> Spring Framework Support for OSGi (JIRA thread)
> http://opensource.atlassian.com/projects/spring/browse/SPR-1802
>
> Spring OSGi Specification (v0.7)
> http://www.springframework.org/osgi/specification
>
> Enrique
>
Re: [OSGi] Status - Commons and Mina Support
Posted by Enrique Rodriguez <en...@gmail.com>.
On 11/21/06, John E. Conlon <jc...@verticon.com> wrote:
> As part of the ongoing effort to update support for OSGi ApacheDS and
> Mina I have committed several OSGi projects to the sandbox/jconlon.
...
This looks like great work! I just took some time to catch up on
Spring-OSGi integration and there certainly is a lot happening there.
I will fire up your code shortly. Some of the resources I read
through were:
Spring OSGi support gaining momentum
http://blog.interface21.com/main/2006/09/07/spring-osgi-support-gaining-momentum/
OSGi and Spring
http://www.osgi.org/blog/2006/08/osgi-and-spring_29.html
Spring Framework Support for OSGi (JIRA thread)
http://opensource.atlassian.com/projects/spring/browse/SPR-1802
Spring OSGi Specification (v0.7)
http://www.springframework.org/osgi/specification
Enrique
Re: [OSGi] Status - Commons and Mina Support
Posted by "John E. Conlon" <jc...@verticon.com>.
Right again. It's the Java 5 optimized branch.
John
On Fri, 2006-11-24 at 12:48 -0800, Cameron Taggart wrote:
> Oops. I just had to make sure I had built the latest mina-1.1 branch.
> I've been using Mina head which is 2.0.0-M1-SNAPSHOT and your
> mina-integration-osgi uses 1.1.0-SNAPSHOT.
>
> svn checkout http://svn.apache.org/repos/asf/mina/branches/1.1/ mina-1.1
> cd mina-1.1
> mvn clean install
>
> my bad,
> Cameron
>
> On 11/24/06, Cameron Taggart <ca...@gmail.com> wrote:
> > Right now I'm stuck on step 3a. It appears that something is
> > requiring the backport concurrent utils. Is it the maven-osgi-plugin?
> > At the moment, I'm not exactly which version is being used. Any idea
> > why there is a apacheds/maven-osgi-plugin?
> >
> > iMac:~/projects/directory-sandbox-jconlon/osgi-mina/integration-osgi
> > ctaggart$ mvn install
> > [INFO] Scanning for projects...
> > [INFO] ----------------------------------------------------------------------------
> > [INFO] Building mina-integration-osgi bundle
> > [INFO] task-segment: [install]
> > [INFO] ----------------------------------------------------------------------------
> > [INFO] [resources:resources]
> > [INFO] Using default encoding to copy filtered resources.
> > [INFO] [compiler:compile]
> > [INFO] No sources to compile
> > [INFO] [resources:testResources]
> > [INFO] Using default encoding to copy filtered resources.
> > [INFO] [compiler:testCompile]
> > [INFO] No sources to compile
> > [INFO] [surefire:test]
> > [INFO] No tests to run.
> > [INFO] [bundle:bundle]
> > [ERROR] Unresolved references to [javax.management, sun.misc] by
> > class(es) on the Bundle-Classpath[Jar:dot]:
> > [edu/emory/mathcs/backport/java/util/concurrent/helpers/Utils$2.class,
> > edu/emory/mathcs/backport/java/util/concurrent/helpers/Utils$SunPerfProvider.class,
> > org/apache/mina/integration/jmx/IoServiceManager.class]
> > org.apache.maven.plugin.MojoFailureException: Found errors, see log
> > at org.apache.felix.tools.maven2.bundleplugin.BundlePlugin.execute(BundlePlugin.java:150)
> > at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:585)
> > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> > at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> > [INFO] ------------------------------------------------------------------------
> > [ERROR] BUILD ERROR
> > [INFO] ------------------------------------------------------------------------
> > [INFO] Found errors, see log
> > [INFO] ------------------------------------------------------------------------
> > [INFO] For more information, run Maven with the -e switch
> > [INFO] ------------------------------------------------------------------------
> > [INFO] Total time: 2 seconds
> > [INFO] Finished at: Fri Nov 24 12:18:07 PST 2006
> > [INFO] Final Memory: 4M/9M
> > [INFO] ------------------------------------------------------------------------
> >
> > Cameron
> >
> > On 11/24/06, John E. Conlon <jc...@verticon.com> wrote:
> > > Right.
> > >
> > > Appreciate any feedback.
> > >
> > > cheers,
> > > John
> > >
> > > On Fri, 2006-11-24 at 10:45 -0800, Cameron Taggart wrote:
> > > > Ah, your over in the ApacheDS sandbox. :)
> > > >
> > > > http://svn.apache.org/viewvc/directory/sandbox/jconlon/
> > > > svn checkout http://svn.apache.org/repos/asf/directory/sandbox/
> > > > directory-sandbox
> > > >
> > > > cheers,
> > > > Cameron
> > > >
> > > > On 11/24/06, Cameron Taggart <ca...@gmail.com> wrote:
> > > > > Hi John, where is your code? I don't see it in the Mina sandbox.
> > > > > http://svn.apache.org/repos/asf/mina/sandbox/
> > > > >
> > > > > Cameron
> > > > >
> > > > > On 11/21/06, John E. Conlon <jc...@verticon.com> wrote:
> > > > > > As part of the ongoing effort to update support for OSGi ApacheDS and
> > > > > > Mina I have committed several OSGi projects to the sandbox/jconlon.
> > > > > > These projects provide:
> > > > > > all the need pieces for OSGi Mina
> > > > > > and lay the initial foundations for a full featured OSGi ADS backend
> > > > > > that I will be committing next week.
> > > > > >
> > > > > > Please check out these projects, build them and try them out in an OSGi
> > > > > > runtime and let me know what you think. If you have questions I will do
> > > > > > my best to answer them.
> > > > > >
> > > > > > If you have not worked with OSGi previously and want to get started
> > > > > > goto:
> > > > > > http://incubator.apache.org/felix/ and read the documentation, download
> > > > > > sources, and build.
> > > > > >
> > > > > > (Have tested the committed projects within the felix and equinox OSGi
> > > > > > runtimes.)
> > > > > >
> > > > > > 1. osgi-commons projects
> > > > > > Both ADS and Mina depend on third party libraries. To offer ADS and
> > > > > > Mina OSGi support these libraries must also support OSGi and be
> > > > > > installed and their packages exported on the OSGi runtime. To facilitate
> > > > > > this support (in an interim basis until the Felix commons project is
> > > > > > initiated or the libraries are made available by their authors as osgi
> > > > > > bundles) within the sandbox/jconlon/osgi-commons directory you will find
> > > > > > simple pom based projects for creating annotated jars (aka OSGi bundles)
> > > > > > for
> > > > > > antlr, commons-collections, commons-lang, and jzlib.
> > > > > >
> > > > > > Note on the maven Plugin:
> > > > > > These projects utilize the new org.apache.felix maven-bundle-plugin to
> > > > > > do the wrapping/annotating of the jars. This plugin offers some unique
> > > > > > features over the first generation maven-osgi-plugin so if you have used
> > > > > > the Enrique's original plugin this one will take a little time getting
> > > > > > used to.
> > > > > >
> > > > > > To build all the commons projects:
> > > > > > cd sandbox/jconlon/osgi-commons
> > > > > > mvn clean install
> > > > > >
> > > > > >
> > > > > > 2. osgi-services
> > > > > >
> > > > > > a, logging-service
> > > > > > Support for an OSGi ApacheDS and Mina will require the slf4j logging
> > > > > > packages to be made available on the OSGi runtime. Unfortunately since
> > > > > > not all library authors have adopted slf4j, some like Spring-OSGi
> > > > > > require commons-logging. So in order to provide the logging packages
> > > > > > that we and our likely functional collaborators will need -
> > > > > >
> > > > > > Within the sandbox/jconlon/osgi-services/logging-service directory you
> > > > > > will find an OSGi Bundle offering an implementation of the OSGi
> > > > > > LogService, library support for Apache slf4j, and slf4j support for
> > > > > > Apache commons-logging. All services are based on the slf4j simple
> > > > > > implementation.
> > > > > >
> > > > > > Configuring logging in an OSGi runtime:
> > > > > > To change the logging configuration from the defaults, create/edit the
> > > > > > configuration properties in the <osgiruntimeWorkingDir>/
> > > > > > conf/log4j.properties file, then stop and restart the bundle.
> > > > > >
> > > > > > b. logging-service-integration-test
> > > > > > This is the OSGi integration-test project for logging-service. This
> > > > > > project builds a OSGi environment, loads various bundles, and tests the
> > > > > > logging-service is doing it's thing. It is strictly optional and will
> > > > > > require downloading and building of the Spring-OSGi sources.
> > > > > > http://www.springframework.org/osgi
> > > > > >
> > > > > >
> > > > > > 3. osgi-mina
> > > > > >
> > > > > > a. integration-osgi
> > > > > > The pom based project in sandbox/jconlon/osgi-mina/integration-osgi is
> > > > > > an OSGi annotated jar/bundle for Mina as requested in
> > > > > > http://issues.apache.org/jira/browse/DIRMINA-27
> > > > > >
> > > > > > For it to resolve in an OSGi it will require the following packages to
> > > > > > be exported in the runtime:
> > > > > >
> > > > > > com.jcraft.jzlib (see #1. above)
> > > > > > org.slf4j, (see #2.a above)
> > > > > > org.springframework.beans.factory,
> > > > > > org.springframework.beans.factory.config,
> > > > > > org.springframework.core.io,
> > > > > > org.springframework.util
> > > > > >
> > > > > > The springframework packages bundled for OSGi are provided in the Spring
> > > > > > OSGi sub project: http://www.springframework.org/osgi
> > > > > >
> > > > > > b. mina-osgi-example
> > > > > > The sandbox/jconlon/osgi-mina/mina-osgi-example is an example of a mina
> > > > > > osgi server application. Based on the mina chat example this
> > > > > > application utilizes Spring-OSGi. The beauty of Spring-OSGi (available
> > > > > > in spring 2.1) is that with it we can create our beans and provide the
> > > > > > wiring without any dependencies on OSGi or for that matter Spring. Cool
> > > > > > eh?
> > > > > > Project also includes a spring-container server client testcase.
> > > > > >
> > > > > >
> > > > > > c. mina-osgi-example-integration-test
> > > > > > This is the OSGi integration-test project for mina-osgi-example. It is
> > > > > > strictly optional and will require downloading and building of the
> > > > > > Spring-OSGi sources at http://www.springframework.org/osgi to get it to
> > > > > > build and run.
> > > > > >
> > > > > > How does it work?
> > > > > > This project builds an OSGi environment, loads Spring-OSGi and bundles
> > > > > > required by Mina and the mina-osgi-example and then starts the mina-
> > > > > > osgi-example. The Spring-OSGi will detect the start of the mina-osgi-
> > > > > > example and find its spring configuration, wire the beans and start the
> > > > > > server. The testcase will bring up a chat client and bounce some
> > > > > > messages at it.
> > > > > >
> > > > > >
> > > > > >
> > > > > > feedback, comments?
> > > > > > John
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> >
>
Re: [OSGi] Status - Commons and Mina Support
Posted by Cameron Taggart <ca...@gmail.com>.
Oops. I just had to make sure I had built the latest mina-1.1 branch.
I've been using Mina head which is 2.0.0-M1-SNAPSHOT and your
mina-integration-osgi uses 1.1.0-SNAPSHOT.
svn checkout http://svn.apache.org/repos/asf/mina/branches/1.1/ mina-1.1
cd mina-1.1
mvn clean install
my bad,
Cameron
On 11/24/06, Cameron Taggart <ca...@gmail.com> wrote:
> Right now I'm stuck on step 3a. It appears that something is
> requiring the backport concurrent utils. Is it the maven-osgi-plugin?
> At the moment, I'm not exactly which version is being used. Any idea
> why there is a apacheds/maven-osgi-plugin?
>
> iMac:~/projects/directory-sandbox-jconlon/osgi-mina/integration-osgi
> ctaggart$ mvn install
> [INFO] Scanning for projects...
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building mina-integration-osgi bundle
> [INFO] task-segment: [install]
> [INFO] ----------------------------------------------------------------------------
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] No sources to compile
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] No sources to compile
> [INFO] [surefire:test]
> [INFO] No tests to run.
> [INFO] [bundle:bundle]
> [ERROR] Unresolved references to [javax.management, sun.misc] by
> class(es) on the Bundle-Classpath[Jar:dot]:
> [edu/emory/mathcs/backport/java/util/concurrent/helpers/Utils$2.class,
> edu/emory/mathcs/backport/java/util/concurrent/helpers/Utils$SunPerfProvider.class,
> org/apache/mina/integration/jmx/IoServiceManager.class]
> org.apache.maven.plugin.MojoFailureException: Found errors, see log
> at org.apache.felix.tools.maven2.bundleplugin.BundlePlugin.execute(BundlePlugin.java:150)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Found errors, see log
> [INFO] ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 2 seconds
> [INFO] Finished at: Fri Nov 24 12:18:07 PST 2006
> [INFO] Final Memory: 4M/9M
> [INFO] ------------------------------------------------------------------------
>
> Cameron
>
> On 11/24/06, John E. Conlon <jc...@verticon.com> wrote:
> > Right.
> >
> > Appreciate any feedback.
> >
> > cheers,
> > John
> >
> > On Fri, 2006-11-24 at 10:45 -0800, Cameron Taggart wrote:
> > > Ah, your over in the ApacheDS sandbox. :)
> > >
> > > http://svn.apache.org/viewvc/directory/sandbox/jconlon/
> > > svn checkout http://svn.apache.org/repos/asf/directory/sandbox/
> > > directory-sandbox
> > >
> > > cheers,
> > > Cameron
> > >
> > > On 11/24/06, Cameron Taggart <ca...@gmail.com> wrote:
> > > > Hi John, where is your code? I don't see it in the Mina sandbox.
> > > > http://svn.apache.org/repos/asf/mina/sandbox/
> > > >
> > > > Cameron
> > > >
> > > > On 11/21/06, John E. Conlon <jc...@verticon.com> wrote:
> > > > > As part of the ongoing effort to update support for OSGi ApacheDS and
> > > > > Mina I have committed several OSGi projects to the sandbox/jconlon.
> > > > > These projects provide:
> > > > > all the need pieces for OSGi Mina
> > > > > and lay the initial foundations for a full featured OSGi ADS backend
> > > > > that I will be committing next week.
> > > > >
> > > > > Please check out these projects, build them and try them out in an OSGi
> > > > > runtime and let me know what you think. If you have questions I will do
> > > > > my best to answer them.
> > > > >
> > > > > If you have not worked with OSGi previously and want to get started
> > > > > goto:
> > > > > http://incubator.apache.org/felix/ and read the documentation, download
> > > > > sources, and build.
> > > > >
> > > > > (Have tested the committed projects within the felix and equinox OSGi
> > > > > runtimes.)
> > > > >
> > > > > 1. osgi-commons projects
> > > > > Both ADS and Mina depend on third party libraries. To offer ADS and
> > > > > Mina OSGi support these libraries must also support OSGi and be
> > > > > installed and their packages exported on the OSGi runtime. To facilitate
> > > > > this support (in an interim basis until the Felix commons project is
> > > > > initiated or the libraries are made available by their authors as osgi
> > > > > bundles) within the sandbox/jconlon/osgi-commons directory you will find
> > > > > simple pom based projects for creating annotated jars (aka OSGi bundles)
> > > > > for
> > > > > antlr, commons-collections, commons-lang, and jzlib.
> > > > >
> > > > > Note on the maven Plugin:
> > > > > These projects utilize the new org.apache.felix maven-bundle-plugin to
> > > > > do the wrapping/annotating of the jars. This plugin offers some unique
> > > > > features over the first generation maven-osgi-plugin so if you have used
> > > > > the Enrique's original plugin this one will take a little time getting
> > > > > used to.
> > > > >
> > > > > To build all the commons projects:
> > > > > cd sandbox/jconlon/osgi-commons
> > > > > mvn clean install
> > > > >
> > > > >
> > > > > 2. osgi-services
> > > > >
> > > > > a, logging-service
> > > > > Support for an OSGi ApacheDS and Mina will require the slf4j logging
> > > > > packages to be made available on the OSGi runtime. Unfortunately since
> > > > > not all library authors have adopted slf4j, some like Spring-OSGi
> > > > > require commons-logging. So in order to provide the logging packages
> > > > > that we and our likely functional collaborators will need -
> > > > >
> > > > > Within the sandbox/jconlon/osgi-services/logging-service directory you
> > > > > will find an OSGi Bundle offering an implementation of the OSGi
> > > > > LogService, library support for Apache slf4j, and slf4j support for
> > > > > Apache commons-logging. All services are based on the slf4j simple
> > > > > implementation.
> > > > >
> > > > > Configuring logging in an OSGi runtime:
> > > > > To change the logging configuration from the defaults, create/edit the
> > > > > configuration properties in the <osgiruntimeWorkingDir>/
> > > > > conf/log4j.properties file, then stop and restart the bundle.
> > > > >
> > > > > b. logging-service-integration-test
> > > > > This is the OSGi integration-test project for logging-service. This
> > > > > project builds a OSGi environment, loads various bundles, and tests the
> > > > > logging-service is doing it's thing. It is strictly optional and will
> > > > > require downloading and building of the Spring-OSGi sources.
> > > > > http://www.springframework.org/osgi
> > > > >
> > > > >
> > > > > 3. osgi-mina
> > > > >
> > > > > a. integration-osgi
> > > > > The pom based project in sandbox/jconlon/osgi-mina/integration-osgi is
> > > > > an OSGi annotated jar/bundle for Mina as requested in
> > > > > http://issues.apache.org/jira/browse/DIRMINA-27
> > > > >
> > > > > For it to resolve in an OSGi it will require the following packages to
> > > > > be exported in the runtime:
> > > > >
> > > > > com.jcraft.jzlib (see #1. above)
> > > > > org.slf4j, (see #2.a above)
> > > > > org.springframework.beans.factory,
> > > > > org.springframework.beans.factory.config,
> > > > > org.springframework.core.io,
> > > > > org.springframework.util
> > > > >
> > > > > The springframework packages bundled for OSGi are provided in the Spring
> > > > > OSGi sub project: http://www.springframework.org/osgi
> > > > >
> > > > > b. mina-osgi-example
> > > > > The sandbox/jconlon/osgi-mina/mina-osgi-example is an example of a mina
> > > > > osgi server application. Based on the mina chat example this
> > > > > application utilizes Spring-OSGi. The beauty of Spring-OSGi (available
> > > > > in spring 2.1) is that with it we can create our beans and provide the
> > > > > wiring without any dependencies on OSGi or for that matter Spring. Cool
> > > > > eh?
> > > > > Project also includes a spring-container server client testcase.
> > > > >
> > > > >
> > > > > c. mina-osgi-example-integration-test
> > > > > This is the OSGi integration-test project for mina-osgi-example. It is
> > > > > strictly optional and will require downloading and building of the
> > > > > Spring-OSGi sources at http://www.springframework.org/osgi to get it to
> > > > > build and run.
> > > > >
> > > > > How does it work?
> > > > > This project builds an OSGi environment, loads Spring-OSGi and bundles
> > > > > required by Mina and the mina-osgi-example and then starts the mina-
> > > > > osgi-example. The Spring-OSGi will detect the start of the mina-osgi-
> > > > > example and find its spring configuration, wire the beans and start the
> > > > > server. The testcase will bring up a chat client and bounce some
> > > > > messages at it.
> > > > >
> > > > >
> > > > >
> > > > > feedback, comments?
> > > > > John
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> >
>
Re: [OSGi] Status - Commons and Mina Support
Posted by Cameron Taggart <ca...@gmail.com>.
Right now I'm stuck on step 3a. It appears that something is
requiring the backport concurrent utils. Is it the maven-osgi-plugin?
At the moment, I'm not exactly which version is being used. Any idea
why there is a apacheds/maven-osgi-plugin?
iMac:~/projects/directory-sandbox-jconlon/osgi-mina/integration-osgi
ctaggart$ mvn install
[INFO] Scanning for projects...
[INFO] ----------------------------------------------------------------------------
[INFO] Building mina-integration-osgi bundle
[INFO] task-segment: [install]
[INFO] ----------------------------------------------------------------------------
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] No sources to compile
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] No tests to run.
[INFO] [bundle:bundle]
[ERROR] Unresolved references to [javax.management, sun.misc] by
class(es) on the Bundle-Classpath[Jar:dot]:
[edu/emory/mathcs/backport/java/util/concurrent/helpers/Utils$2.class,
edu/emory/mathcs/backport/java/util/concurrent/helpers/Utils$SunPerfProvider.class,
org/apache/mina/integration/jmx/IoServiceManager.class]
org.apache.maven.plugin.MojoFailureException: Found errors, see log
at org.apache.felix.tools.maven2.bundleplugin.BundlePlugin.execute(BundlePlugin.java:150)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Found errors, see log
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2 seconds
[INFO] Finished at: Fri Nov 24 12:18:07 PST 2006
[INFO] Final Memory: 4M/9M
[INFO] ------------------------------------------------------------------------
Cameron
On 11/24/06, John E. Conlon <jc...@verticon.com> wrote:
> Right.
>
> Appreciate any feedback.
>
> cheers,
> John
>
> On Fri, 2006-11-24 at 10:45 -0800, Cameron Taggart wrote:
> > Ah, your over in the ApacheDS sandbox. :)
> >
> > http://svn.apache.org/viewvc/directory/sandbox/jconlon/
> > svn checkout http://svn.apache.org/repos/asf/directory/sandbox/
> > directory-sandbox
> >
> > cheers,
> > Cameron
> >
> > On 11/24/06, Cameron Taggart <ca...@gmail.com> wrote:
> > > Hi John, where is your code? I don't see it in the Mina sandbox.
> > > http://svn.apache.org/repos/asf/mina/sandbox/
> > >
> > > Cameron
> > >
> > > On 11/21/06, John E. Conlon <jc...@verticon.com> wrote:
> > > > As part of the ongoing effort to update support for OSGi ApacheDS and
> > > > Mina I have committed several OSGi projects to the sandbox/jconlon.
> > > > These projects provide:
> > > > all the need pieces for OSGi Mina
> > > > and lay the initial foundations for a full featured OSGi ADS backend
> > > > that I will be committing next week.
> > > >
> > > > Please check out these projects, build them and try them out in an OSGi
> > > > runtime and let me know what you think. If you have questions I will do
> > > > my best to answer them.
> > > >
> > > > If you have not worked with OSGi previously and want to get started
> > > > goto:
> > > > http://incubator.apache.org/felix/ and read the documentation, download
> > > > sources, and build.
> > > >
> > > > (Have tested the committed projects within the felix and equinox OSGi
> > > > runtimes.)
> > > >
> > > > 1. osgi-commons projects
> > > > Both ADS and Mina depend on third party libraries. To offer ADS and
> > > > Mina OSGi support these libraries must also support OSGi and be
> > > > installed and their packages exported on the OSGi runtime. To facilitate
> > > > this support (in an interim basis until the Felix commons project is
> > > > initiated or the libraries are made available by their authors as osgi
> > > > bundles) within the sandbox/jconlon/osgi-commons directory you will find
> > > > simple pom based projects for creating annotated jars (aka OSGi bundles)
> > > > for
> > > > antlr, commons-collections, commons-lang, and jzlib.
> > > >
> > > > Note on the maven Plugin:
> > > > These projects utilize the new org.apache.felix maven-bundle-plugin to
> > > > do the wrapping/annotating of the jars. This plugin offers some unique
> > > > features over the first generation maven-osgi-plugin so if you have used
> > > > the Enrique's original plugin this one will take a little time getting
> > > > used to.
> > > >
> > > > To build all the commons projects:
> > > > cd sandbox/jconlon/osgi-commons
> > > > mvn clean install
> > > >
> > > >
> > > > 2. osgi-services
> > > >
> > > > a, logging-service
> > > > Support for an OSGi ApacheDS and Mina will require the slf4j logging
> > > > packages to be made available on the OSGi runtime. Unfortunately since
> > > > not all library authors have adopted slf4j, some like Spring-OSGi
> > > > require commons-logging. So in order to provide the logging packages
> > > > that we and our likely functional collaborators will need -
> > > >
> > > > Within the sandbox/jconlon/osgi-services/logging-service directory you
> > > > will find an OSGi Bundle offering an implementation of the OSGi
> > > > LogService, library support for Apache slf4j, and slf4j support for
> > > > Apache commons-logging. All services are based on the slf4j simple
> > > > implementation.
> > > >
> > > > Configuring logging in an OSGi runtime:
> > > > To change the logging configuration from the defaults, create/edit the
> > > > configuration properties in the <osgiruntimeWorkingDir>/
> > > > conf/log4j.properties file, then stop and restart the bundle.
> > > >
> > > > b. logging-service-integration-test
> > > > This is the OSGi integration-test project for logging-service. This
> > > > project builds a OSGi environment, loads various bundles, and tests the
> > > > logging-service is doing it's thing. It is strictly optional and will
> > > > require downloading and building of the Spring-OSGi sources.
> > > > http://www.springframework.org/osgi
> > > >
> > > >
> > > > 3. osgi-mina
> > > >
> > > > a. integration-osgi
> > > > The pom based project in sandbox/jconlon/osgi-mina/integration-osgi is
> > > > an OSGi annotated jar/bundle for Mina as requested in
> > > > http://issues.apache.org/jira/browse/DIRMINA-27
> > > >
> > > > For it to resolve in an OSGi it will require the following packages to
> > > > be exported in the runtime:
> > > >
> > > > com.jcraft.jzlib (see #1. above)
> > > > org.slf4j, (see #2.a above)
> > > > org.springframework.beans.factory,
> > > > org.springframework.beans.factory.config,
> > > > org.springframework.core.io,
> > > > org.springframework.util
> > > >
> > > > The springframework packages bundled for OSGi are provided in the Spring
> > > > OSGi sub project: http://www.springframework.org/osgi
> > > >
> > > > b. mina-osgi-example
> > > > The sandbox/jconlon/osgi-mina/mina-osgi-example is an example of a mina
> > > > osgi server application. Based on the mina chat example this
> > > > application utilizes Spring-OSGi. The beauty of Spring-OSGi (available
> > > > in spring 2.1) is that with it we can create our beans and provide the
> > > > wiring without any dependencies on OSGi or for that matter Spring. Cool
> > > > eh?
> > > > Project also includes a spring-container server client testcase.
> > > >
> > > >
> > > > c. mina-osgi-example-integration-test
> > > > This is the OSGi integration-test project for mina-osgi-example. It is
> > > > strictly optional and will require downloading and building of the
> > > > Spring-OSGi sources at http://www.springframework.org/osgi to get it to
> > > > build and run.
> > > >
> > > > How does it work?
> > > > This project builds an OSGi environment, loads Spring-OSGi and bundles
> > > > required by Mina and the mina-osgi-example and then starts the mina-
> > > > osgi-example. The Spring-OSGi will detect the start of the mina-osgi-
> > > > example and find its spring configuration, wire the beans and start the
> > > > server. The testcase will bring up a chat client and bounce some
> > > > messages at it.
> > > >
> > > >
> > > >
> > > > feedback, comments?
> > > > John
> > > >
> > > >
> > > >
> > >
> >
>
>
Re: [OSGi] Status - Commons and Mina Support
Posted by "John E. Conlon" <jc...@verticon.com>.
Right.
Appreciate any feedback.
cheers,
John
On Fri, 2006-11-24 at 10:45 -0800, Cameron Taggart wrote:
> Ah, your over in the ApacheDS sandbox. :)
>
> http://svn.apache.org/viewvc/directory/sandbox/jconlon/
> svn checkout http://svn.apache.org/repos/asf/directory/sandbox/
> directory-sandbox
>
> cheers,
> Cameron
>
> On 11/24/06, Cameron Taggart <ca...@gmail.com> wrote:
> > Hi John, where is your code? I don't see it in the Mina sandbox.
> > http://svn.apache.org/repos/asf/mina/sandbox/
> >
> > Cameron
> >
> > On 11/21/06, John E. Conlon <jc...@verticon.com> wrote:
> > > As part of the ongoing effort to update support for OSGi ApacheDS and
> > > Mina I have committed several OSGi projects to the sandbox/jconlon.
> > > These projects provide:
> > > all the need pieces for OSGi Mina
> > > and lay the initial foundations for a full featured OSGi ADS backend
> > > that I will be committing next week.
> > >
> > > Please check out these projects, build them and try them out in an OSGi
> > > runtime and let me know what you think. If you have questions I will do
> > > my best to answer them.
> > >
> > > If you have not worked with OSGi previously and want to get started
> > > goto:
> > > http://incubator.apache.org/felix/ and read the documentation, download
> > > sources, and build.
> > >
> > > (Have tested the committed projects within the felix and equinox OSGi
> > > runtimes.)
> > >
> > > 1. osgi-commons projects
> > > Both ADS and Mina depend on third party libraries. To offer ADS and
> > > Mina OSGi support these libraries must also support OSGi and be
> > > installed and their packages exported on the OSGi runtime. To facilitate
> > > this support (in an interim basis until the Felix commons project is
> > > initiated or the libraries are made available by their authors as osgi
> > > bundles) within the sandbox/jconlon/osgi-commons directory you will find
> > > simple pom based projects for creating annotated jars (aka OSGi bundles)
> > > for
> > > antlr, commons-collections, commons-lang, and jzlib.
> > >
> > > Note on the maven Plugin:
> > > These projects utilize the new org.apache.felix maven-bundle-plugin to
> > > do the wrapping/annotating of the jars. This plugin offers some unique
> > > features over the first generation maven-osgi-plugin so if you have used
> > > the Enrique's original plugin this one will take a little time getting
> > > used to.
> > >
> > > To build all the commons projects:
> > > cd sandbox/jconlon/osgi-commons
> > > mvn clean install
> > >
> > >
> > > 2. osgi-services
> > >
> > > a, logging-service
> > > Support for an OSGi ApacheDS and Mina will require the slf4j logging
> > > packages to be made available on the OSGi runtime. Unfortunately since
> > > not all library authors have adopted slf4j, some like Spring-OSGi
> > > require commons-logging. So in order to provide the logging packages
> > > that we and our likely functional collaborators will need -
> > >
> > > Within the sandbox/jconlon/osgi-services/logging-service directory you
> > > will find an OSGi Bundle offering an implementation of the OSGi
> > > LogService, library support for Apache slf4j, and slf4j support for
> > > Apache commons-logging. All services are based on the slf4j simple
> > > implementation.
> > >
> > > Configuring logging in an OSGi runtime:
> > > To change the logging configuration from the defaults, create/edit the
> > > configuration properties in the <osgiruntimeWorkingDir>/
> > > conf/log4j.properties file, then stop and restart the bundle.
> > >
> > > b. logging-service-integration-test
> > > This is the OSGi integration-test project for logging-service. This
> > > project builds a OSGi environment, loads various bundles, and tests the
> > > logging-service is doing it's thing. It is strictly optional and will
> > > require downloading and building of the Spring-OSGi sources.
> > > http://www.springframework.org/osgi
> > >
> > >
> > > 3. osgi-mina
> > >
> > > a. integration-osgi
> > > The pom based project in sandbox/jconlon/osgi-mina/integration-osgi is
> > > an OSGi annotated jar/bundle for Mina as requested in
> > > http://issues.apache.org/jira/browse/DIRMINA-27
> > >
> > > For it to resolve in an OSGi it will require the following packages to
> > > be exported in the runtime:
> > >
> > > com.jcraft.jzlib (see #1. above)
> > > org.slf4j, (see #2.a above)
> > > org.springframework.beans.factory,
> > > org.springframework.beans.factory.config,
> > > org.springframework.core.io,
> > > org.springframework.util
> > >
> > > The springframework packages bundled for OSGi are provided in the Spring
> > > OSGi sub project: http://www.springframework.org/osgi
> > >
> > > b. mina-osgi-example
> > > The sandbox/jconlon/osgi-mina/mina-osgi-example is an example of a mina
> > > osgi server application. Based on the mina chat example this
> > > application utilizes Spring-OSGi. The beauty of Spring-OSGi (available
> > > in spring 2.1) is that with it we can create our beans and provide the
> > > wiring without any dependencies on OSGi or for that matter Spring. Cool
> > > eh?
> > > Project also includes a spring-container server client testcase.
> > >
> > >
> > > c. mina-osgi-example-integration-test
> > > This is the OSGi integration-test project for mina-osgi-example. It is
> > > strictly optional and will require downloading and building of the
> > > Spring-OSGi sources at http://www.springframework.org/osgi to get it to
> > > build and run.
> > >
> > > How does it work?
> > > This project builds an OSGi environment, loads Spring-OSGi and bundles
> > > required by Mina and the mina-osgi-example and then starts the mina-
> > > osgi-example. The Spring-OSGi will detect the start of the mina-osgi-
> > > example and find its spring configuration, wire the beans and start the
> > > server. The testcase will bring up a chat client and bounce some
> > > messages at it.
> > >
> > >
> > >
> > > feedback, comments?
> > > John
> > >
> > >
> > >
> >
>
Re: [OSGi] Status - Commons and Mina Support
Posted by Cameron Taggart <ca...@gmail.com>.
Ah, your over in the ApacheDS sandbox. :)
http://svn.apache.org/viewvc/directory/sandbox/jconlon/
svn checkout http://svn.apache.org/repos/asf/directory/sandbox/
directory-sandbox
cheers,
Cameron
On 11/24/06, Cameron Taggart <ca...@gmail.com> wrote:
> Hi John, where is your code? I don't see it in the Mina sandbox.
> http://svn.apache.org/repos/asf/mina/sandbox/
>
> Cameron
>
> On 11/21/06, John E. Conlon <jc...@verticon.com> wrote:
> > As part of the ongoing effort to update support for OSGi ApacheDS and
> > Mina I have committed several OSGi projects to the sandbox/jconlon.
> > These projects provide:
> > all the need pieces for OSGi Mina
> > and lay the initial foundations for a full featured OSGi ADS backend
> > that I will be committing next week.
> >
> > Please check out these projects, build them and try them out in an OSGi
> > runtime and let me know what you think. If you have questions I will do
> > my best to answer them.
> >
> > If you have not worked with OSGi previously and want to get started
> > goto:
> > http://incubator.apache.org/felix/ and read the documentation, download
> > sources, and build.
> >
> > (Have tested the committed projects within the felix and equinox OSGi
> > runtimes.)
> >
> > 1. osgi-commons projects
> > Both ADS and Mina depend on third party libraries. To offer ADS and
> > Mina OSGi support these libraries must also support OSGi and be
> > installed and their packages exported on the OSGi runtime. To facilitate
> > this support (in an interim basis until the Felix commons project is
> > initiated or the libraries are made available by their authors as osgi
> > bundles) within the sandbox/jconlon/osgi-commons directory you will find
> > simple pom based projects for creating annotated jars (aka OSGi bundles)
> > for
> > antlr, commons-collections, commons-lang, and jzlib.
> >
> > Note on the maven Plugin:
> > These projects utilize the new org.apache.felix maven-bundle-plugin to
> > do the wrapping/annotating of the jars. This plugin offers some unique
> > features over the first generation maven-osgi-plugin so if you have used
> > the Enrique's original plugin this one will take a little time getting
> > used to.
> >
> > To build all the commons projects:
> > cd sandbox/jconlon/osgi-commons
> > mvn clean install
> >
> >
> > 2. osgi-services
> >
> > a, logging-service
> > Support for an OSGi ApacheDS and Mina will require the slf4j logging
> > packages to be made available on the OSGi runtime. Unfortunately since
> > not all library authors have adopted slf4j, some like Spring-OSGi
> > require commons-logging. So in order to provide the logging packages
> > that we and our likely functional collaborators will need -
> >
> > Within the sandbox/jconlon/osgi-services/logging-service directory you
> > will find an OSGi Bundle offering an implementation of the OSGi
> > LogService, library support for Apache slf4j, and slf4j support for
> > Apache commons-logging. All services are based on the slf4j simple
> > implementation.
> >
> > Configuring logging in an OSGi runtime:
> > To change the logging configuration from the defaults, create/edit the
> > configuration properties in the <osgiruntimeWorkingDir>/
> > conf/log4j.properties file, then stop and restart the bundle.
> >
> > b. logging-service-integration-test
> > This is the OSGi integration-test project for logging-service. This
> > project builds a OSGi environment, loads various bundles, and tests the
> > logging-service is doing it's thing. It is strictly optional and will
> > require downloading and building of the Spring-OSGi sources.
> > http://www.springframework.org/osgi
> >
> >
> > 3. osgi-mina
> >
> > a. integration-osgi
> > The pom based project in sandbox/jconlon/osgi-mina/integration-osgi is
> > an OSGi annotated jar/bundle for Mina as requested in
> > http://issues.apache.org/jira/browse/DIRMINA-27
> >
> > For it to resolve in an OSGi it will require the following packages to
> > be exported in the runtime:
> >
> > com.jcraft.jzlib (see #1. above)
> > org.slf4j, (see #2.a above)
> > org.springframework.beans.factory,
> > org.springframework.beans.factory.config,
> > org.springframework.core.io,
> > org.springframework.util
> >
> > The springframework packages bundled for OSGi are provided in the Spring
> > OSGi sub project: http://www.springframework.org/osgi
> >
> > b. mina-osgi-example
> > The sandbox/jconlon/osgi-mina/mina-osgi-example is an example of a mina
> > osgi server application. Based on the mina chat example this
> > application utilizes Spring-OSGi. The beauty of Spring-OSGi (available
> > in spring 2.1) is that with it we can create our beans and provide the
> > wiring without any dependencies on OSGi or for that matter Spring. Cool
> > eh?
> > Project also includes a spring-container server client testcase.
> >
> >
> > c. mina-osgi-example-integration-test
> > This is the OSGi integration-test project for mina-osgi-example. It is
> > strictly optional and will require downloading and building of the
> > Spring-OSGi sources at http://www.springframework.org/osgi to get it to
> > build and run.
> >
> > How does it work?
> > This project builds an OSGi environment, loads Spring-OSGi and bundles
> > required by Mina and the mina-osgi-example and then starts the mina-
> > osgi-example. The Spring-OSGi will detect the start of the mina-osgi-
> > example and find its spring configuration, wire the beans and start the
> > server. The testcase will bring up a chat client and bounce some
> > messages at it.
> >
> >
> >
> > feedback, comments?
> > John
> >
> >
> >
>
Re: [OSGi] Status - Commons and Mina Support
Posted by Cameron Taggart <ca...@gmail.com>.
Hi John, where is your code? I don't see it in the Mina sandbox.
http://svn.apache.org/repos/asf/mina/sandbox/
Cameron
On 11/21/06, John E. Conlon <jc...@verticon.com> wrote:
> As part of the ongoing effort to update support for OSGi ApacheDS and
> Mina I have committed several OSGi projects to the sandbox/jconlon.
> These projects provide:
> all the need pieces for OSGi Mina
> and lay the initial foundations for a full featured OSGi ADS backend
> that I will be committing next week.
>
> Please check out these projects, build them and try them out in an OSGi
> runtime and let me know what you think. If you have questions I will do
> my best to answer them.
>
> If you have not worked with OSGi previously and want to get started
> goto:
> http://incubator.apache.org/felix/ and read the documentation, download
> sources, and build.
>
> (Have tested the committed projects within the felix and equinox OSGi
> runtimes.)
>
> 1. osgi-commons projects
> Both ADS and Mina depend on third party libraries. To offer ADS and
> Mina OSGi support these libraries must also support OSGi and be
> installed and their packages exported on the OSGi runtime. To facilitate
> this support (in an interim basis until the Felix commons project is
> initiated or the libraries are made available by their authors as osgi
> bundles) within the sandbox/jconlon/osgi-commons directory you will find
> simple pom based projects for creating annotated jars (aka OSGi bundles)
> for
> antlr, commons-collections, commons-lang, and jzlib.
>
> Note on the maven Plugin:
> These projects utilize the new org.apache.felix maven-bundle-plugin to
> do the wrapping/annotating of the jars. This plugin offers some unique
> features over the first generation maven-osgi-plugin so if you have used
> the Enrique's original plugin this one will take a little time getting
> used to.
>
> To build all the commons projects:
> cd sandbox/jconlon/osgi-commons
> mvn clean install
>
>
> 2. osgi-services
>
> a, logging-service
> Support for an OSGi ApacheDS and Mina will require the slf4j logging
> packages to be made available on the OSGi runtime. Unfortunately since
> not all library authors have adopted slf4j, some like Spring-OSGi
> require commons-logging. So in order to provide the logging packages
> that we and our likely functional collaborators will need -
>
> Within the sandbox/jconlon/osgi-services/logging-service directory you
> will find an OSGi Bundle offering an implementation of the OSGi
> LogService, library support for Apache slf4j, and slf4j support for
> Apache commons-logging. All services are based on the slf4j simple
> implementation.
>
> Configuring logging in an OSGi runtime:
> To change the logging configuration from the defaults, create/edit the
> configuration properties in the <osgiruntimeWorkingDir>/
> conf/log4j.properties file, then stop and restart the bundle.
>
> b. logging-service-integration-test
> This is the OSGi integration-test project for logging-service. This
> project builds a OSGi environment, loads various bundles, and tests the
> logging-service is doing it's thing. It is strictly optional and will
> require downloading and building of the Spring-OSGi sources.
> http://www.springframework.org/osgi
>
>
> 3. osgi-mina
>
> a. integration-osgi
> The pom based project in sandbox/jconlon/osgi-mina/integration-osgi is
> an OSGi annotated jar/bundle for Mina as requested in
> http://issues.apache.org/jira/browse/DIRMINA-27
>
> For it to resolve in an OSGi it will require the following packages to
> be exported in the runtime:
>
> com.jcraft.jzlib (see #1. above)
> org.slf4j, (see #2.a above)
> org.springframework.beans.factory,
> org.springframework.beans.factory.config,
> org.springframework.core.io,
> org.springframework.util
>
> The springframework packages bundled for OSGi are provided in the Spring
> OSGi sub project: http://www.springframework.org/osgi
>
> b. mina-osgi-example
> The sandbox/jconlon/osgi-mina/mina-osgi-example is an example of a mina
> osgi server application. Based on the mina chat example this
> application utilizes Spring-OSGi. The beauty of Spring-OSGi (available
> in spring 2.1) is that with it we can create our beans and provide the
> wiring without any dependencies on OSGi or for that matter Spring. Cool
> eh?
> Project also includes a spring-container server client testcase.
>
>
> c. mina-osgi-example-integration-test
> This is the OSGi integration-test project for mina-osgi-example. It is
> strictly optional and will require downloading and building of the
> Spring-OSGi sources at http://www.springframework.org/osgi to get it to
> build and run.
>
> How does it work?
> This project builds an OSGi environment, loads Spring-OSGi and bundles
> required by Mina and the mina-osgi-example and then starts the mina-
> osgi-example. The Spring-OSGi will detect the start of the mina-osgi-
> example and find its spring configuration, wire the beans and start the
> server. The testcase will bring up a chat client and bounce some
> messages at it.
>
>
>
> feedback, comments?
> John
>
>
>