atom feed16 messages in org.apache.incubator.sling-devRe: Annoyance during update of bundles
FromSent OnAttachments
Alexander KlimetschekAug 29, 2008 7:50 am 
Tobias BocanegraAug 29, 2008 11:33 am 
Alexander SaarAug 29, 2008 11:58 am 
Jukka ZittingAug 29, 2008 12:17 pm 
Alexander KlimetschekAug 30, 2008 1:58 am 
Carsten ZiegelerAug 30, 2008 2:15 am 
Tobias BocanegraAug 30, 2008 9:47 am 
Felix MeschbergerAug 31, 2008 10:58 pm 
Bertrand DelacretazSep 1, 2008 12:04 am 
Alexander KlimetschekSep 1, 2008 12:54 am 
Felix MeschbergerSep 1, 2008 2:02 am 
Alexander KlimetschekSep 1, 2008 2:16 am 
Carsten ZiegelerSep 1, 2008 2:31 am 
Alexander KlimetschekSep 1, 2008 3:05 am 
Felix MeschbergerSep 2, 2008 1:15 am 
Bertrand DelacretazSep 2, 2008 4:14 am 
Subject:Re: Annoyance during update of bundles
From:Alexander Saar (alex@googlemail.com)
Date:Aug 29, 2008 11:58:13 am
List:org.apache.incubator.sling-dev

Am 29.08.2008 um 16:50 schrieb Alexander Klimetschek:

Hi all,

when I update a bundle containing a servlet (eg. servlet path = /bin/myservlet) and I hit my curl command for testing that servlet (POST to /bin/myservlet + a few specific params) too fast, ie. in the time when the old version of the bundle is gone, but the new version is not yet started, and hence nothing is registered under /bin/myservlet, the request is handled by the SlingPostServlet, which in this case creates a new JCR node under /bin/myservlet.

Any ideas how to circumvent this little annoyance during development?

if you don't need it for your development and testing you can just disable the SlingPostServlet service in the Felix console

regards alex