From dev-return-104178-archive-asf-public=cust-asf.ponee.io@sling.apache.org Mon Mar 2 08:28:32 2020 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 1DA0D18062C for ; Mon, 2 Mar 2020 09:28:32 +0100 (CET) Received: (qmail 7118 invoked by uid 500); 2 Mar 2020 08:28:31 -0000 Mailing-List: contact dev-help@sling.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sling.apache.org Delivered-To: mailing list dev@sling.apache.org Received: (qmail 7105 invoked by uid 99); 2 Mar 2020 08:28:31 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.159) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Mar 2020 08:28:31 +0000 Received: from [10.136.171.141] (unknown [193.105.139.131]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id CF7F72234 for ; Mon, 2 Mar 2020 08:28:30 +0000 (UTC) Subject: Re: [Starter] Startup detection not working reliable anymore To: dev@sling.apache.org References: <6854858e-fa57-6bb1-3ccb-dddeee46a54e@apache.org> <8FC77D70-355C-4778-A7B9-D597A7158A51@gmx.de> From: Carsten Ziegeler Message-ID: Date: Mon, 2 Mar 2020 09:28:29 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: <8FC77D70-355C-4778-A7B9-D597A7158A51@gmx.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Thanks Konrad, I'm struggling a little bit here as this worked with the initial version we had - that was not a sophisticated implementation but did the trick and most importantly did not present exceptions on startup to potentially new users. It seems we now have switched to a general approach which doesn't solve the simple use case anymore but instead requires changes to other parts as well. I'm not saying that the general approach is wrong or the additional work is wrong, but the simple use case for the starter could be achieved with a much simpler solution without annoying users. Regards Carsten On 02.03.2020 09:12, Konrad Windszus wrote: > This has been adjusted in the context of https://issues.apache.org/jira/browse/SLING-8418 . > I think the exceptions are related to the order: https://issues.apache.org/jira/browse/SLING-8355 . > Maybe Georg can explain the exceptions a bit better... > > Konrad > >> On 2. Mar 2020, at 09:06, Carsten Ziegeler wrote: >> >> Hi, >> >> some time back we added a mechanism that - on startup of the starter application - display a screen telling the user that the server is starting up. >> >> Over time this mechanism got changed - I don't know what exactly it is using today - but it is not working reliable anymore. If you hit refresh you are presented with different exceptions. Eventually, after pressing refresh some more times, the startup page is there. >> >> This means, depending on when you open the browser, you either get the startup notice or an exception - clearly not a great user experience. >> >> It would be great if this could be fixed. >> >> >> Regards >> Carsten >> -- >> Carsten Ziegeler >> Adobe Research Switzerland >> cziegeler@apache.org > > -- -- Carsten Ziegeler Adobe Research Switzerland cziegeler@apache.org