Now I have to make my application work.

So did it work for you? Do you have your app up and running? Please note: the URL will be http://localhost:8080/myapp-version/ instead of http://localhost:8080/myapp/ like grails run-app does it

I don’t know why the Spring DM jars won’t get resolved and downloaded, they are specified as dependencies of the OSGi plugin. Maybe the SpringSource Enterprise Repository (EBR) ditched them or was offline?

BTW, the code on GitHub (http://github.com/jetztgradnet/grails-osgi-plugin/) is now up to date, if you want to have a look or change anything.

Have fun,

Wolfgang

Did you really stay up till 3am to finish this for me? If so, an even bigger thanks.

Additionally I needed some jars to fix UNRESOLVED DEPENDENCIES:

wget http://osgi-in-action.googlecode.com/svn-history/r21/trunk/lib/blueprint/spring-osgi-io-2.0.0.M1.jar
$ mv spring-osgi-io-2.0.0.M1.jar lib/
wget http://osgi-in-action.googlecode.com/svn-history/r21/trunk/lib/blueprint/spring-osgi-core-2.0.0.M1.jar
mv spring-osgi-core-2.0.0.M1.jar lib/

I put in some work and created a snapshot version of OSGi plugin 0.2, which you can use instead of the 0.1 version.

0.2-SNAPSHOT does not need Pax Web anymore. Hibernate and GORM works in this release.

To try it out, perform the following steps:
1. Create a Grails App (using Grails 1.3.2)
2. Install OSGi plugin 0.2 SNAPSHOT:
grails install-plugin http://github.com/downloads/jetztgradnet/grails-osgi-plugin/grails-osgi-0.2.zip
3. Change Config.groovy
Set grails.logging.jul.usebridge = false
4. Create some Domain classes and controllers
5. Run app in OSGi environment
grails run-bundle -forceBundle
The parameter -forceBundle is necessary, whenever something changed in your app, otherwise the bundle won’t be rebuilt.

Have fun,

Wolfgang

Almost there!

Now I see:

org.ops4j.pax.runner.platform.PlatformException: [http://download.eclipse.org/equinox/drops/R-3.4.2-200902111700/org.eclipse.equinox.supplement_1.1.0.v20080421-2006.jar] could not be downloaded

Seems it might need to come from http://archive.eclipse.org/equinox/drops/R-3.4.2-200902111700/ instead?

thanks for your hard work!

The latter commands fail, because you are not in the directory containing the grails OSGi plugin, but in the directory, where (I assume) you built pax runner or pax web.

With Grails 1.3.2 you don’t need to repackage the OSGi plugin, if you simply change BuildConfig.groovy in your test app to contain a line like this:

grails.plugin.location.’Osgi’ = ‘/path/to/changed/grails-osgi-plugin’

This way Grails uses the plugin inline and you don’t have to package and migrate it.

HTH,

Wolfgang

adjust the links in grails-osgiplugin/grails-app/paxrunner-grails.profile

Ok, so, for others interested, this is what I fixed up in /Users/martincleaver/SoftwareDevelopment/Grails/grails-osgi-plugin/grails-app/paxrunner-grails.profile:

Found this section:

# Pax Web including Jetty (6.1.9)
scan-bundle:mvn:org.ops4j.pax.web/pax-web-api/0.8.0-SNAPSHOT
scan-bundle:mvn:org.ops4j.pax.web/pax-web-spi/0.8.0-SNAPSHOT
scan-bundle:mvn:org.ops4j.pax.web/pax-web-runtime/0.8.0-SNAPSHOT
scan-bundle:mvn:org.ops4j.pax.web/pax-web-jsp/0.8.0-SNAPSHOT
scan-bundle:mvn:org.ops4j.pax.web/pax-web-jetty/0.8.0-SNAPSHOT
scan-bundle:mvn:org.ops4j.pax.web/pax-web-extender-war/0.8.0-SNAPSHOT
scan-bundle:mvn:org.ops4j.pax.web/pax-web-extender-whiteboard/0.8.0-SNAPSHOT

And replaced with

scan-bundle:file:/Users/martincleaver/SoftwareDevelopment/OSGi/paxweb/web-0.7.1/pax-web-api/target/pax-web-api-0.7.1.jar
scan-bundle:file:/Users/martincleaver/SoftwareDevelopment/OSGi/paxweb/web-0.7.1/pax-web-extender-war/target/pax-web-extender-war-0.7.1.jar
scan-bundle:file:/Users/martincleaver/SoftwareDevelopment/OSGi/paxweb/web-0.7.1/pax-web-extender-whiteboard/target/pax-web-extender-whiteboard-0.7.1.jar
scan-bundle:file:/Users/martincleaver/SoftwareDevelopment/OSGi/paxweb/web-0.7.1/pax-web-jetty/target/pax-web-jetty-0.7.1.jar
scan-bundle:file:/Users/martincleaver/SoftwareDevelopment/OSGi/paxweb/web-0.7.1/pax-web-jetty-bundle/target/pax-web-jetty-bundle-0.7.1.jar
scan-bundle:file:/Users/martincleaver/SoftwareDevelopment/OSGi/paxweb/web-0.7.1/pax-web-jsp/target/pax-web-jsp-0.7.1.jar
scan-bundle:file:/Users/martincleaver/SoftwareDevelopment/OSGi/paxweb/web-0.7.1/pax-web-runtime/target/pax-web-runtime-0.7.1.jar
scan-bundle:file:/Users/martincleaver/SoftwareDevelopment/OSGi/paxweb/web-0.7.1/pax-web-spi/target/pax-web-spi-0.7.1.jar

# find ~/SoftwareDevelopment/OSGi/paxweb/web-0.7.1 -name ‘*.jar’

Now, simply running grails run-bundle in my target app is not enough, because I am not yet using the version of grails-osgi-plugin that I just modified. For that I must

grails package-plugin
Welcome to Grails 1.3.2 – http://grails.org/
Licensed under Apache Standard License 2.0
Grails home is set to: /Users/martincleaver/grails

Base Directory: /Users/martincleaver/My Documents/5.SoftwareDevelopment/OSGi/paxrunner/runner-build
Resolving dependencies…
Dependencies resolved in 1323ms.
Running script /Users/martincleaver/grails/scripts/PackagePlugin_.groovy
Environment set to development
Application is pre-Grails 0.5, please run: grails upgrade

martincleaver@ip-85-160-218-111.eurotel.cz:~/SoftwareDevelopment/OSGi/paxrunner/runner-build 22:23:06 559$ grails upgrade
Welcome to Grails 1.3.2 – http://grails.org/
Licensed under Apache Standard License 2.0
Grails home is set to: /Users/martincleaver/grails

Base Directory: /Users/martincleaver/My Documents/5.SoftwareDevelopment/OSGi/paxrunner/runner-build
Resolving dependencies…
Dependencies resolved in 1768ms.
/Users/martincleaver/My Documents/5.SoftwareDevelopment/OSGi/paxrunner/runner-build does not appear to be part of a Grails application.
The following commands are supported outside of a project:
add-proxy
clear-proxy
create-app
create-plugin
help
list-plugins
package-plugin
plugin-info
remove-proxy
set-proxy
Run ‘grails help’ for a complete list of available scripts.

So, there’s something fishy going on that prevents me from building the new version. Any clues? Thanks, Martin.

I’m actively working on version 0.2 of the OSGi plugin, which does not need PAX Web anymore.

Ok. Might be wise as I did notice that development of paxweb has slowed down – no release since Oct 2009. Let’s hope though.

jetztgradnet :
The 0.8.0 snapshot is required

Looks like Paxweb 0.8.0 wasn’t released, http://wiki.ops4j.org/display/paxweb/Download shows 0.7.1 as the latest finished build. https://scm.ops4j.org/repos/ops4j/qa/pax/ shows web-0.7.2/ as the latest in dev.

you might be able to check out PaxWeb, build 0.8.0-snapshot yourself and adjust the links in grails-osgiplugin/grails-app/paxrunner-grails.profile

I checked out 0.7.1 and am presently doing a ‘mvn package’ to build it. From there I’ll try these changes.

If its quick to try I’ll certainly have a go. I agree I would need the GORM functionality.

Cheers, Martin.