From dev-return-69205-archive-asf-public=cust-asf.ponee.io@myfaces.apache.org Tue Feb 27 00:11:29 2018 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 [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 7CC4418064A for ; Tue, 27 Feb 2018 00:11:28 +0100 (CET) Received: (qmail 82115 invoked by uid 500); 26 Feb 2018 23:11:27 -0000 Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Development" Delivered-To: mailing list dev@myfaces.apache.org Received: (qmail 82097 invoked by uid 99); 26 Feb 2018 23:11:26 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Feb 2018 23:11:26 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 3A9EDC0040 for ; Mon, 26 Feb 2018 23:11:26 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.88 X-Spam-Level: * X-Spam-Status: No, score=1.88 tagged_above=-999 required=6.31 tests=[AC_DIV_BONANZA=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id yrov088F5UzO for ; Mon, 26 Feb 2018 23:11:24 +0000 (UTC) Received: from mail-lf0-f43.google.com (mail-lf0-f43.google.com [209.85.215.43]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id E0D975FAD9 for ; Mon, 26 Feb 2018 23:11:23 +0000 (UTC) Received: by mail-lf0-f43.google.com with SMTP id r80so24726085lfe.13 for ; Mon, 26 Feb 2018 15:11:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=3btB2vR4TxybixKQRQbPRP3xAu/eW1Q71ZfvrbD2s0Y=; b=VN5PxS+JgLGl5veGJDJHi0Kc1xRVT7sG9Du935X3H6PSHKjuzEKJChBnxZukIJw3I6 P7mFmd0mkCtmI0vAGodx3S4Z3GWLe98Agw/kXRQGhH1VHQH5McRiefWjPomkEv07ULaA GKcRff+xy1h+DyNHX9emEQYS95qvEb6p1T7iHBjlb1wUVIGbq/mw/xMIBU0GywE9RhjB 9bkfJ3EmGgalxmsUrm5gsYrlU5kNGlbJh/4ETCCmFRd/Pm0c5hCxJw9a6iQu1ZywP/Ff SZdziNNT/zmVaP9BHTooudGFUaxURtCjkCaZBaay+jh0fpUmHbInMv+2ExurRna6X7hQ RO/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=3btB2vR4TxybixKQRQbPRP3xAu/eW1Q71ZfvrbD2s0Y=; b=dhOul0QJVJNvAOH9giYECi5YGQzMricugvhNwkuRO/HCgoZ7kqH5xvS95lNAb87bXN iwkASbj4ayEngr+v/6TM5X/+sjcgi1dm9H9uhuuZ5R/+mQWEmqsb6hFMpC4/ksMJdyk7 p/jW+llyr6xk2dhTBB1CBjeFHGOfFoI4Pj19EBPxAIioEWSEHNtMjXuCZdgCpJRbe/ty +hqtqi3CAg42HEd+AZWxbZcOKkZ5b/4tICoVUActhvNGwtwNbkjipjezJ2XR4kkZsnoQ /1DoCYx1Z9kXhNT0exH5r0Zg+x+E3+45jYQVmtzz+pBJBkS7k4v0SuymXMIDon1pCaRX kUSA== X-Gm-Message-State: APf1xPDtMPMBk+w+D9bg5l2o/WRF3j79gm5pazAJ0JfQvj+HHKx8YlVD qKxKBGRaEJ3ThlTlztWCaITA21Ipr1W5ao6xQ0c7dHLb X-Google-Smtp-Source: AG47ELtVHeew958tQv66QQ70QL3UnRQVRFMt5RKtD71cFUx71vYUzuW36K/yvLToM1h7mt7SOEho2VrmbXZjW1fCNzA= X-Received: by 10.25.212.19 with SMTP id l19mr8609473lfg.83.1519686682484; Mon, 26 Feb 2018 15:11:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.46.99.221 with HTTP; Mon, 26 Feb 2018 15:11:21 -0800 (PST) From: Thomas Andraschko Date: Tue, 27 Feb 2018 00:11:21 +0100 Message-ID: Subject: @ManagedBean @PostConstruct on Jetty To: MyFaces Development Content-Type: multipart/alternative; boundary="001a11406476e12488056625a0e1" --001a11406476e12488056625a0e1 Content-Type: text/plain; charset="UTF-8" Hi, AFAICS Tomcat7LifecycleProvider is also used on Jetty. I wonder how it worked in the past on Jetty? Does Jetty use some parts of Tomcat? It seems that the packages are available, also on Jetty. So i assume that Jetty uses some parts of Tomcat under the hood and therefore the tomcat-api package with the InstanceManager is available. Probably in the past Jetty also delivered other packages, so the DefaultInstanceManager was available and @PostConstruct worked. Now, with Jetty 9.3.x there is only a SimpleInstanceManager, which does absolutely nothing. If my assumptions are correct, it also affects older MF releases, when the users would upgrade the jetty versions. How should we fix this? Regards, Thomas --001a11406476e12488056625a0e1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,
<= br>
AFAICS Tomcat7LifecycleProvider is also used on Jetty.
I wonder how it worked in the past on Jetty?

Does Jet= ty use some parts of Tomcat?
It seems that the packages are availa= ble, also on Jetty.
So i assume that Jetty uses some parts of Tomc= at under the hood and therefore the tomcat-api package with the InstanceMan= ager is available.
Probably in the past Jetty also delivered other= packages, so the DefaultInstanceManager was available and @PostConstruct w= orked.
Now, with Jetty 9.3.x there is only a SimpleInstanceManager= , which does absolutely nothing.

If my assumptions are correct, it a= lso affects older MF releases, when the users would upgrade the jetty versi= ons.

How should we fix this?

Regards,
T= homas

--001a11406476e12488056625a0e1--