What makes a bundle draggable on to a server instance ?

[Beta User]

I have a bundle with an OSGI bundle project nature, and a manifest that imports some bundles and libraries, exports some packages, and an OSGI context that exports a service. All the configuration seems to be OK based on sight checking.

If I drag my bundle on to an instance of S2AP in Eclipse nothing happens at all (not added to list of deployed bundles, no logs).

On the assumption that this drag and drop is a short cut way of exporting the bundle and dropping it into the usr bunlde dir, what is it about a project that makes if droppable on to a server instance, or put more succinctly, why doesn't mine work ?

[Sam Brannen]

Paul, if you open your project's properties, have you selected "SpringSource AP v1.0" as a Targeted Runtime, and is that target the same server onto which you're dragging your bundle?

- Sam

[Joris Kuipers]

Also, to respond to your assumption, dragging the project on the server could be compared to dropping the exported jar in the pickup directory, NOT the usr bundle directory. There is a difference: for instance, bundles installed through the pickup dir or admin console cannot be used by other bundles through Import-Bundle, I think.

Joris

[Beta User]

Have you restarted Eclipse? We are seeing the same behavior you describe, where you have the manifest and the OSGi bundle nature, but until we restart Eclipse the AP plugin doesn't seem to recognize project is compatible.

[Beta User]

Thanks for this. I had to remove an obsolete utility module facet before I could add in the Targeted Runtime, after that I could drag it on and start it.

Am I right in thinking that bundles dropped on to the server instance can be used by other bundles ? This seems to be exactly how thing's work in Dave Syer's Spring Batch on S2AP blog here:

http://blog.springsource.com/main/2008/05/30/running-a-spring-batch-job-in-the-springsource-aplication-platform/

[Andy Wilkinson]

Bundles deployed individually can be used by other application bundles. Bundles deployed within a PAR file are automatically scoped by the Platform such they can't be used by bundles that are not part of the PAR.

Regards,
Andy