Thanks for the solution. Neil, you suggested to set "org.osgi.framework.storage" property, but this properly is available in OSGi Release 4 not in OSGi Release 3.
Do you have any solution compatible to OSGi Release 4. Regards Vikash Agrawal Senior Design Engineer GE Healthcare T: +9180 4088 1415 M: +9198 8673 2249 www.gehealthcare.com John F Welch Technology Center, #152, EPIP Phase V, Whitefield, Bangalore, India 560066 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Craig Phillips Sent: Wednesday, February 09, 2011 7:43 PM To: OSGi Developer Mail List Subject: RE: [osgi-dev] OSGi-eclipse files creation issues Hi, I pretty much use OSGi strictly in an embedding architecture, usually I provide my own distributed architecture by riding other frameworks. In this usage paradigm the nature of "data storage area" is, as you might expect, a little "murky"; Luckily, I have storage, as most applications will, versus some sort of RAM device and what have you. With that said, I have learned to live with the "data storage area" requirement by a simple / standard "practice": I have a "template" storage area and the config.properties file has a few "REPLACE_ME" tokens sprinkled about. At container instantiation time (reminder - this is embedded), my "manager" code will create/manage the "data storage area" on a per container basis. Whether or not anyone wants to debate this scheme/paradigm, that's up to you... I've been using it to significant operational success for several years... At least with Felix, "it just works" (which is why I stopped using Microsoft and I strictly use linux [ubuntu]); If you have something that "just works", you tend to stick to it. Now, I still haven't forgotten the topic of "source bundles" and I've created my own one-off of Felix in which I can natively deploy source code and have the framework do the build by simply looking at the manifest, but that's a different discussion thread. Cheers... Craig ________________________________________ From: [email protected] [[email protected]] on behalf of Neil Bartlett [[email protected]] Sent: Wednesday, February 09, 2011 8:13 AM To: OSGi Developer Mail List Subject: Re: [osgi-dev] OSGi-eclipse files creation issues Hi Vikash, All OSGi frameworks need to create a data storage area, to allow them to persist and restore the state of bundles. You can choose to erase the storage area on *startup* by setting the "org.osgi.framework.storage.clean" property. You can also specify the location of the storage area by setting the "org.osgi.framework.storage" property. Be aware that if you erase the storage area then the OSGi framework will return to its default "empty" state. Regards, Neil On Wed, Feb 9, 2011 at 11:05 AM, AGRAWAL, VIKASH (GE Healthcare) <[email protected]> wrote: > Hi > > Scenario: I have created an OSGi bundle by exporting it from Eclipse > IDE and kept it in a folder and launched OSGi by executing the jar > file (org.eclipse.osgi_3.3.0.v20070530.jar), which is in > D:\Vikash\bundles\OSGi-server folder. > > Issue: Every time it's creating some files under > D:\Vikash\bundles\OSGi-server\configuration\org.eclipse.osgi\bundles > (configuration\org.eclipse.osgi\bundles folder was created automatically). > Is there any configuration that under some circumstances we can make > it to delete all these files. > > Regards > Vikash Agrawal > Senior Design Engineer > GE Healthcare > T: +9180 4088 1415 > M: +9198 8673 2249 > www.gehealthcare.com > John F Welch Technology Center, #152, EPIP Phase V, Whitefield, > Bangalore, India 560066 > > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev > _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
