Comments on: Creating OSGi bundles http://blog.springsource.org/2008/02/18/creating-osgi-bundles/ The voice of SpringSource Wed, 08 Feb 2012 17:31:53 +0000 hourly 1 http://wordpress.org/?v=3.1.1 By: Andrew Swan http://blog.springsource.org/2008/02/18/creating-osgi-bundles/comment-page-1/#comment-236313 Andrew Swan Fri, 20 Jan 2012 11:06:41 +0000 http://blog.springsource.com/main/2008/02/18/creating-osgi-bundles/#comment-236313 Nice write-up, Costin, thanks! Nice write-up, Costin, thanks!

]]> By: منتديات http://blog.springsource.org/2008/02/18/creating-osgi-bundles/comment-page-1/#comment-173917 منتديات Sat, 26 Jun 2010 20:13:20 +0000 http://blog.springsource.com/main/2008/02/18/creating-osgi-bundles/#comment-173917 I created bundles for third party jars using BND plugin. All packages are exported. But, still when I try to use it, I get "The constructor is not accessible due to restriction on required library ". Any idea on why this happens and how to avoid this? I created bundles for third party jars using BND plugin. All packages are exported. But, still when I try to use it, I get "The constructor is not accessible due to restriction on required library ". Any idea on why this happens and how to avoid this?

]]> By: OSGi bez irytacji http://blog.springsource.org/2008/02/18/creating-osgi-bundles/comment-page-1/#comment-171559 OSGi bez irytacji Tue, 09 Mar 2010 11:26:35 +0000 http://blog.springsource.com/main/2008/02/18/creating-osgi-bundles/#comment-171559 [...] Creating OSGi Bundles [...] [...] Creating OSGi Bundles [...]

]]> By: OSGi bez irytacji http://blog.springsource.org/2008/02/18/creating-osgi-bundles/comment-page-1/#comment-171560 OSGi bez irytacji Tue, 09 Mar 2010 11:26:35 +0000 http://blog.springsource.com/main/2008/02/18/creating-osgi-bundles/#comment-171560 [...] Creating OSGi Bundles [...] [...] Creating OSGi Bundles [...]

]]> By: Raja http://blog.springsource.org/2008/02/18/creating-osgi-bundles/comment-page-1/#comment-171267 Raja Mon, 08 Feb 2010 00:23:58 +0000 http://blog.springsource.com/main/2008/02/18/creating-osgi-bundles/#comment-171267 I created bundles for third party jars using BND plugin. All packages are exported. But, still when I try to use it, I get "The constructor is not accessible due to restriction on required library ". Any idea on why this happens and how to avoid this? Thanks, - Raja. I created bundles for third party jars using BND plugin. All packages are exported. But, still when I try to use it, I get "The constructor is not accessible due to restriction on required library ". Any idea on why this happens and how to avoid this?

Thanks,

- Raja.

]]> By: Hello world! http://blog.springsource.org/2008/02/18/creating-osgi-bundles/comment-page-1/#comment-169501 Hello world! Tue, 17 Nov 2009 09:25:06 +0000 http://blog.springsource.com/main/2008/02/18/creating-osgi-bundles/#comment-169501 [...] as for OSGi, you can read what Matt Raible wrote. Don’t forget to skim Costin Leau’s blog entry discussing OSGi bundles (”bundle” is just a fancy alias for “jar”, I’m [...] [...] as for OSGi, you can read what Matt Raible wrote. Don't forget to skim Costin Leau's blog entry discussing OSGi bundles ("bundle" is just a fancy alias for "jar", I'm [...]

]]> By: brian.h.gt http://blog.springsource.org/2008/02/18/creating-osgi-bundles/comment-page-1/#comment-167515 brian.h.gt Wed, 08 Jul 2009 03:07:43 +0000 http://blog.springsource.com/main/2008/02/18/creating-osgi-bundles/#comment-167515 "But due to the fact that the project i was working on was not structured in a set of subprojects so that i could have used eclipse pde for my developing but rather consisted of one huge classpath during build time" Yeah, it looks like bnd works great for projects that are not structured... but I'm disappointed that it doesn't work for projects that _are_ structured. Working with Eclipse and separating your bundles into logical projects with individual manifests is, in my opinion, cleaner and more modular. However, I have not found bnd to support this. Hiding packages (so that two classes with the same name and package could potentially exist in separate bundles and not exported) is a feature of OSGi and using one giant unstructured src/bin folder destroys that! In my perfect world: 1) The manifest should be maintained in only _one_ spot. Generating it every time doesn't work well with version control or for just running your src straight out of the box with an IDE. Saying, "Oh, by the way... you have to run these ANT targets before you open Eclipse" isn't fun. 2) Compiling a bundle with ANT would be easy with multiple projects, source folders, and manifests. I won't be using bnd as a build tool. "But due to the fact that the project i was working on was not structured in a set of subprojects so that i could have used eclipse pde for my developing but rather consisted of one huge classpath during build time"

Yeah, it looks like bnd works great for projects that are not structured… but I'm disappointed that it doesn't work for projects that _are_ structured.

Working with Eclipse and separating your bundles into logical projects with individual manifests is, in my opinion, cleaner and more modular. However, I have not found bnd to support this. Hiding packages (so that two classes with the same name and package could potentially exist in separate bundles and not exported) is a feature of OSGi and using one giant unstructured src/bin folder destroys that!

In my perfect world:
1) The manifest should be maintained in only _one_ spot. Generating it every time doesn't work well with version control or for just running your src straight out of the box with an IDE. Saying, "Oh, by the way… you have to run these ANT targets before you open Eclipse" isn't fun.
2) Compiling a bundle with ANT would be easy with multiple projects, source folders, and manifests.

I won't be using bnd as a build tool.

]]> By: links for 2009-04-23 « Niels’ blog http://blog.springsource.org/2008/02/18/creating-osgi-bundles/comment-page-1/#comment-164252 links for 2009-04-23 « Niels’ blog Fri, 24 Apr 2009 06:05:06 +0000 http://blog.springsource.com/main/2008/02/18/creating-osgi-bundles/#comment-164252 [...] SpringSource Team Blog » Creating OSGi bundles (tags: bnd osgi spring tutorial) [...] [...] SpringSource Team Blog » Creating OSGi bundles (tags: bnd osgi spring tutorial) [...]

]]> By: SpringSource Team Blog » Exposing the boot classpath in OSGi http://blog.springsource.org/2008/02/18/creating-osgi-bundles/comment-page-1/#comment-143483 SpringSource Team Blog » Exposing the boot classpath in OSGi Mon, 19 Jan 2009 20:18:40 +0000 http://blog.springsource.com/main/2008/02/18/creating-osgi-bundles/#comment-143483 [...] to the bootstrapping classpath from OSGi, without bundling it. To express package dependencies, bundles use the OSGi directive inside their manifests - mainly Export-Package and Import-Package for [...] [...] to the bootstrapping classpath from OSGi, without bundling it. To express package dependencies, bundles use the OSGi directive inside their manifests – mainly Export-Package and Import-Package for [...]

]]> By: Bundles in OSGi « Sukasom http://blog.springsource.org/2008/02/18/creating-osgi-bundles/comment-page-1/#comment-114897 Bundles in OSGi « Sukasom Mon, 28 Jul 2008 11:15:34 +0000 http://blog.springsource.com/main/2008/02/18/creating-osgi-bundles/#comment-114897 [...] There is a new concept called “Bundle.” A bundle is actually a group of required Java files and resouces.  It is similar to a Jar file which is a zip file containing java class file and resources. However, a Jar file does not have information about OSGi which is used for managing the software component life cycle. It allows developers to add or remove a Java component (bundle) during runtime. Read here for more info on OSGi. Costin Leau wrote a good article on Bundle. [...] [...] There is a new concept called "Bundle." A bundle is actually a group of required Java files and resouces.  It is similar to a Jar file which is a zip file containing java class file and resources. However, a Jar file does not have information about OSGi which is used for managing the software component life cycle. It allows developers to add or remove a Java component (bundle) during runtime. Read here for more info on OSGi. Costin Leau wrote a good article on Bundle. [...]

]]>