Hi Andy, >We have asked for such a feature in a future OSGi release since >the virtual bundle stuff we do in Spring-OSGi is a little tacky >(re-writing jars on the fly). >I don't know what the status of this is but it seems a universally desired feature. That's interesting. Have you (or someone else in your team) already written a RfP (Request for Proposal) for it? If not, I would propose that we do it (I have learned that writing a RfP is the first step to get something into OSGi :-)
In SCA we have the JAR files (e.g. the Bindings) which we would like to deploy in OSGi (without repackaging them as OSGi bundles in advance). The idea is to have a directory containing the JAR files which will be observed by a Provisioning Service. Whenever a JAR will be added, the Service takes it, reads the SCDL file (containing the information about exports/imports), generates on the fly the bundle and installs/starts it. We started working on a prototype for this Provisioning Service. I had a look to your BundleFactoryBean and MavenBundleManager and I 'borrowed' some parts of it (re-writing jars on the fly). Hope this is ok. I'm optimistic that it will fulfill our needs, but I would appreciate if OSGi would provide the virtual bundle feature. Best regards Nicole -----Original Message----- From: Andy Piper [mailto:[EMAIL PROTECTED] Sent: Monday, December 18, 2006 4:57 PM To: tuscany-dev@ws.apache.org Cc: tuscany-dev@ws.apache.org Subject: Re: OSGi Binding At 22:14 09/11/2006, Jim Marino wrote: >in a war, it may go in the /lib directory. For OSGi bindle fragments, >is there a deployment API/mechanism where I can take a plain jar (i.e. >no OSGi manifest entries), hand it to the OSGI container and declare >that it is a fragment (maybe it is something specific to Equinox)? We have asked for such a feature in a future OSGi release since the virtual bundle stuff we do in Spring-OSGi is a little tacky (re-writing jars on the fly). I don't know what the status of this is but it seems a universally desired feature. andy _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]