Hi Am 31.05.2012 um 16:06 schrieb sam ”:
> I'm using: > System Bundle org.apache.felix.framework 3.0.7 Ok. So you might be hitting FELIX-2741 and/or FELIX-2822. You might want to update the framework to 3.0.9 or newer. > > It's part of CQ 5.4 If you are using CQ you might want to use the Sling JCR Install feature available with and deploy a CRX content package with your bundles, which you can also do using a cURL request. Regards Felix > > On Thu, May 31, 2012 at 2:43 AM, Felix Meschberger <[email protected]>wrote: > >> Hi, >> >> Am 24.05.2012 um 13:40 schrieb sam ”: >> >>> so, I guess no one has written a multiple bundle deployment script? >>> >>> why are there so many options? >> >> Because there are so many needs and there just are so many options. The >> right one always depends on your requirements. >> >> Regards >> Felix >> >>> >>> what's the best way to deploy multiple bundles? of course it'll depend. >> all >>> different bundle deployment options and ups and downs should be >> documented >>> on homepage or wiki. >>> >>> >>> >>> >>> >>> On Thu, May 24, 2012 at 5:22 AM, Carsten Ziegeler <[email protected] >>> wrote: >>> >>>> Or use the Sling Installer in combination with the Sling file install >>>> bundle, so you can just drop your bundles into a configured dir. >>>> >>>> Carsten >>>> >>>> 2012/5/24 Felix Meschberger <[email protected]>: >>>>> Hi, >>>>> >>>>> Am 23.05.2012 um 19:06 schrieb sam ”: >>>>> >>>>>> Ah, thanks. >>>>>> >>>>>> Meanwhile, is there a better way to deploy 10 or so bundles? >>>>>> I can put sleeps between curl commands.. but I was wondering if >> there's >>>> a >>>>>> way to take felix down and rsync bundles to some location in the felix >>>>>> server. >>>>> >>>>> You might leverage the Sling JCR Install functionality. >>>>> >>>>> Just make sure you store the bundles in a single JCR transaction: >>>>> >>>>> Session s = acquireSession(); >>>>> ... store all bundles in /apps/**/install ... >>>>> s. save(); >>>>> >>>>> Regards >>>>> Felix >>>>> >>>>>> >>>>>> >>>>>> On Wed, May 23, 2012 at 4:06 AM, Felix Meschberger < >> [email protected] >>>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> Am 22.05.2012 um 22:52 schrieb sam ”: >>>>>>> >>>>>>>> Problem of multiple [email protected] >>>>>>> [email protected] >>>>>>>> .... >>>>>>>> >>>>>>>> is that bundles become Installed state, not Active state. >>>>>>> >>>>>>> Hmm, if you supplied the bundlestart parameter, it should start them, >>>> but >>>>>>> .... >>>>>>> >>>>>>> Unfortunately, this is done completely wrong and I have to come back >>>> to my >>>>>>> earlier remark: The Web Console sould probably implement a proper >>>> queue for >>>>>>> installations. Because currently, even though you can upload multiple >>>>>>> bundles, each bundle will be installed in its own thread thus you are >>>> back >>>>>>> to field one. >>>>>>> >>>>>>> I have created FELIX-3523 [1] to track that. >>>>>>> >>>>>>> Regards >>>>>>> Felix >>>>>>> >>>>>>> [1] https://issues.apache.org/jira/browse/FELIX-3523 >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Mon, May 21, 2012 at 10:06 AM, Felix Meschberger < >>>> [email protected] >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> No, the console installs the bundles asynchronously. >>>>>>>>> >>>>>>>>> But you could upload all the bundles with a single curl command >> with >>>> the >>>>>>>>> bundlefile parameter repeated to list each bundle. >>>>>>>>> >>>>>>>>> Regards >>>>>>>>> Felix >>>>>>>>> >>>>>>>>> PS: thinking out loud, the web console could run a single thread >> for >>>>>>>>> installation and queue such requests ... (You might report an >> issue, >>>> if >>>>>>> you >>>>>>>>> like the idea ;- ) >>>>>>>>> >>>>>>>>> Am 21.05.2012 um 15:55 schrieb sam ”: >>>>>>>>> >>>>>>>>>> Hey, >>>>>>>>>> >>>>>>>>>> My deployment script uses curl command: >>>>>>>>>> curl -u admin:admin -F "action=install" -F "_noredir_=_noredir_" >> -F >>>>>>>>>> "[email protected]" -F "bundlestart=start" -F >>>>>>> "bundlestartlevel=20" >>>>>>>>>> -F "refreshPackages=true" " >>>>>>> http://localhost:4502/system/console/install" >>>>>>>>>> curl -u admin:admin -F "action=install" -F "_noredir_=_noredir_" >> -F >>>>>>>>>> "[email protected]" -F "bundlestart=start" -F >>>>>>> "bundlestartlevel=20" >>>>>>>>>> -F "refreshPackages=true" " >>>>>>> http://localhost:4502/system/console/install" >>>>>>>>>> ... >>>>>>>>>> curl -u admin:admin -F "action=install" -F "_noredir_=_noredir_" >> -F >>>>>>>>>> "[email protected]" -F "bundlestart=start" -F >>>>>>>>> "bundlestartlevel=20" >>>>>>>>>> -F "refreshPackages=true" " >>>>>>> http://localhost:4502/system/console/install" >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Each curl command returns very fast. Unless I put `sleep 10` >>>> between >>>>>>>>>> curl commands, I have to `kill -9` felix instance. >>>>>>>>>> >>>>>>>>>> Is there a way to configure web console so that it sends out HTTP >>>>>>>>> response >>>>>>>>>> only after the bundle is completely installed? It looks like I am >>>>>>> sending >>>>>>>>>> install request for bundle2.jar while felix has not finished >>>>>>> installing >>>>>>>>>> bundle1.jar. >>>>>>>>> >>>>>>>>> >>>>>>>>> >> --------------------------------------------------------------------- >>>>>>>>> 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] >>>>>>> >>>>>>> >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>> >>>> >>>> >>>> -- >>>> Carsten Ziegeler >>>> [email protected] >>>> >>>> --------------------------------------------------------------------- >>>> 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] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

