Hi You are completely right, that is the way to go but before I migrate those bundles to ConfigAdming I should make the run for now somehow.
i guess I'll live with the --vmo option until I can migrate them Thanks a lot Cartlos On Jan 7, 2011, at 11:40 AM, Toni Menzel wrote: umm.. maybe those 20 properties are the problem ?? To me its the same as defining functions having 20+ parameters. Any chance to consolidate the parameters? Just trying to show off another point of view. Also, depending on how far you are into OSGi, configuring via System Property is not really OSGi-like (not dynamic). Why not leverage ConfigAdmin ? Toni On Fri, Jan 7, 2011 at 3:35 PM, Carlos Quiroz <[email protected]<mailto:[email protected]>> wrote: Hi Thanks, yes I was meaning that but I was hoping that I could pass a properties file and those could be added to the system properties config.ini I have several of those bundles with more or less 20 properties in total so making the --vmo option contain all those 20 doesn't sound very maintainable Perhaps pax-runner could take an option like --extra.system.properties=../conf/system.properties which can be used to add extra system properties to the container Carlos On Jan 7, 2011, at 11:27 AM, Toni Menzel wrote: Check http://paxrunner.ops4j.org/display/paxrunner/Java+runtime+options Pax Runner generates that felix.ini (for example) and passes the stuff you supply in --vmo (see option above) just into the felix configuration file (just like you did it before) Is it what you mean? On Fri, Jan 7, 2011 at 2:53 PM, Carlos Quiroz <[email protected]<mailto:[email protected]>> wrote: Hi Thanks for the quick answer. Basically I have some old bundles that use BundleContext.getProperty to read some configuration values I want to pass them if possible as a properties file (I can pass them as system properties adding a vmOptions=-D...) so I thought that using the felix.config.properties should be the way to go but that file is set by pax-runner to be felix/config.ini which is generated by pax-runner I'm trying to have a way to add properties to the config.ini file generated by pax-runner or find another way to pass these properties to felix Regards Carlos On Jan 7, 2011, at 10:45 AM, Niclas Hedhman wrote: > Not sure exactly what you are using it for. Could this help; > http://paxrunner.ops4j.org/display/paxrunner/Specify+options+in+an+file > ?? > > On Fri, Jan 7, 2011 at 9:36 PM, Carlos Quiroz > <[email protected]<mailto:[email protected]>> wrote: >> Hi >> >> First of all thanks for all the great pax-tools, I'm using pax-construct and >> pax-runner plus the pax-logging and confman services and they have been >> quite useful >> >> I'm using felix as my container and I need to pass some bundle properties >> which I'd normally do using the felix.config.properties file. However using >> pax-runner that property is always set to be felix/config.ini which is a >> file generated by pax-runner >> >> Is there any way to specify properties to be set in the generated config.ini? >> >> Thanks >> Carlos >> _______________________________________________ >> general mailing list >> [email protected]<mailto:[email protected]> >> http://lists.ops4j.org/mailman/listinfo/general >> > > > > -- > Niclas Hedhman, Software Developer > http://www.qi4j.org<http://www.qi4j.org/> - New Energy for Java > > I live here; http://tinyurl.com/3xugrbk > I work here; http://tinyurl.com/24svnvk > I relax here; http://tinyurl.com/2cgsug _______________________________________________ general mailing list [email protected]<mailto:[email protected]> http://lists.ops4j.org/mailman/listinfo/general -- Toni Menzel || http://okidokiteam.com<http://okidokiteam.com/> _______________________________________________ general mailing list [email protected]<mailto:[email protected]> http://lists.ops4j.org/mailman/listinfo/general -- Toni Menzel || http://okidokiteam.com<http://okidokiteam.com/>
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
