Comments for A Day At The Races

Comment on Groovy & Grails on OSGi by Wolfgang Schell

Wolfgang Schell — Mon, 06 Feb 2012 21:40:18 +0000

Hi Jon, the OSGi plugin replaces some of Grails' dependencies with corresponding bundles from SpinrgSource Enterprise Bundle Repository (EBR), which contains bundle-ized versions of many standard java library. The problem is, that these dependencies are currently more or less hard coded. You might be able to get it to run by tweaking scripts/_Osgi.groovy and scripts/_Events.groovy, where all the replacement bundles and dependencies are defined. You can find the complete source code of the OSGi plugin here. When running it in Virgo, you should remove all tomcat bundles referenced in the scripts mentioned above, as Tomcat is provided in the Virgo Web and Virgo Nano Web installations. HTH, Wolfgang

Comment on Groovy & Grails on OSGi by Jon

Jon — Mon, 06 Feb 2012 18:00:37 +0000

@Wolfgang Schell Thanks for the reply. I'm working with a Grails 1.3.7 app at the moment (Haven't moved to 2.0 yet). I'm trying to get the app running as a OSGi bundle. I'm new to OSGi and have been fighting with it for a week now. I've been bundling a default grails app with only the OSGi plugin installed and have been getting a lot of dependency errors on startup in both virgo 2.1.1 and 3.0.2. The use case is a web platform that can be built upon by adding many separate web applications. I believe that OSGi is the answer to our problems but can't seem to get it figured out.

Comment on Groovy & Grails on OSGi by Wolfgang Schell

Wolfgang Schell — Mon, 30 Jan 2012 21:51:45 +0000

Hi Jon,

I did not get that much feedback on the OSGi plugin and am currently working on other stuff (as time permits, the Grails OSGi plugin is a hobby only). Do you have interest in the plugin? Or do you use it already with an older Grails version? What is your environment and use case? I still want to update the plugin to Grails 2.0, but didn’t get around to it yet.

Cheers,

Wolfgang

Comment on Groovy & Grails on OSGi by Jon

Jon — Mon, 30 Jan 2012 21:25:14 +0000

I take it since it’s been a year and a half since the 0.2.1 release, that development on this plug-in is no longer happening?

Comment on How to customize an Amazon Elastic Beanstalk instance by Franklin Dattein

Franklin Dattein — Thu, 27 Oct 2011 01:46:24 +0000

I have wasted hours trying to customize an AMI started from Beanstalk console, before I found your article.

Thanks for sharing!

Comment on How to customize an Amazon Elastic Beanstalk instance by Wolfgang Schell

Wolfgang Schell — Mon, 23 May 2011 19:37:30 +0000

Thanks

In your customized AMI you can change the timezone using standard Linux configuration tools. If you need a different timezone for your Java app only, you could simply add a ServletContextListener, which sets the timezone using TimeZone#setDefault().

Comment on How to customize an Amazon Elastic Beanstalk instance by Boomie

Boomie — Sat, 21 May 2011 19:45:35 +0000

Your tutorials *have* been awesome. I’ve been reading them, and am now a fan.

I did have one question I thought you might be able to answer quickly: Should I be able to change the time zone of the instance using an AMI file?

Comment on How to customize an Amazon Elastic Beanstalk instance by Greg

Greg — Tue, 19 Apr 2011 02:19:06 +0000

Thanks Wolfgang! Your tutorials have been great!

Comment on Grails on OSGi (2): First steps by Wolfgang Schell

Wolfgang Schell — Thu, 10 Feb 2011 15:18:09 +0000

Hi Arian,

will have a look at it tonight or tomorrow.

There are some more required changes, i.e. allow regex when replacing libs in _Events.groovy (so they don’t depend on single versions). Otherwise this breaks with every new dependency or version change.
I also plan to replace parts of _Osgi.groovy with my groovyx.osgi module and replace Spring DM with Eclipse Gemini Blueprint. But this takes some more time.

Wolfgang

Comment on Grails on OSGi (2): First steps by Arian

Arian — Thu, 10 Feb 2011 13:26:53 +0000

Thanks Wolfgang, I’ll replace _Event.groovy right now.
I also noticed that bundle-manifest.patch doesn’t seem to work with the 1.3.6 release. I was studying the changes that still need to be made on _GrailsWar.groovy.

target “war” looks fine on grails 1.3.6, except the part related to resourceList that still needs to be changed.

target(createDescriptor:”Creates the WEB-INF/grails.xml file used to load Grails classes in WAR mode”) {
- def resourceList = pluginSettings.getArtefactResources()
+ def resourceList = GrailsResourceLoaderHolder.resourceLoader.getResources()