Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Jetty 12 schedule?
  • From: "Cantor, Scott" <cantor.2@xxxxxxx>
  • Date: Wed, 9 Nov 2022 21:07:52 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=2; mx.microsoft.com 1; spf=pass (sender ip is 128.146.163.15) smtp.rcpttodomain=eclipse.org smtp.mailfrom=osu.edu; dmarc=pass (p=none sp=none pct=100) action=none header.from=osu.edu; dkim=pass (signature was verified) header.d=osu.edu; arc=pass (0 oda=1 ltdi=1 spf=[1,1,smtp.mailfrom=osu.edu] dkim=[1,1,header.d=osu.edu] dmarc=[1,1,header.from=osu.edu])
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=osu.edu; dmarc=pass action=none header.from=osu.edu; dkim=pass header.d=osu.edu; arc=none
  • Arc-message-signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=un78QYZpi+tSVsOeRaBFUediEdzs1nQQiGKkeJY7MJk=; b=ZJ8ruE4NiioqltMtKArFydHy8VyG/lLhQsZwBKqeSQwilNms/4PUamxEmIhSsXYq2pNUWcveSxQ31UM9Elwfc0gByl15LAxd2ZoCC2ncYurWNfm4xQHQUg/7smr+WbO3MfypWlzO/wN54OHO1iLKwR+0mAe5K6eE3CtrDJ+YMyN3NmYs/rkZZBEfSterAJFhcy6sMXDcATDk063sN5DbYgl1OwPkunPLECeY8o+lO0v0PP/Ae38cEpNLogBxHgAtMhSaVe936RReUx3XchMxWSgCPBb+h4O/mNsqtnTQ5jT58FE8n+eFE+6pff99Bii13qqPmsAdP+aDYDZcyApTCA==
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=un78QYZpi+tSVsOeRaBFUediEdzs1nQQiGKkeJY7MJk=; b=ZMdXP9PWmJg8qrZ0SANSS9Mpt9lIgWqDQXcEil7/ZbRuH6QClpbJ1mKT0o8OZ63Tj0FPr8XlAruH9kRH0bNQY9ru7Phn6L+vLM6EYgN0IDQG7qfdJzYr9uSYl0RxUGfVusW9vIBaiC9+zsGzsQU8+PJhx15L9m2+JK3Op3DfzkGpHtBENYwNDacGZAYSGjxwSI5y4PbKSAoFK9zkA645HyvxFGYwSWTztNmkLcRgEBre20nu6kfpgevWavZKmXYE9yGqfbw6ZFH/hAi/d+2cOa/CUKVywrnoCSR2x3Q41ro+We1UCEmGExuWloIvcl8FVqTsYmV+j5Y8+NMaP+GEAQ==
  • Arc-seal: i=2; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=pass; b=LAWbYZbtywPBC7zLFs/BiY+2DjsYTtOev92oyuRQCyqfeBnIezPhmTIk52XbO8tQ/ktfvkM9iVxqE8OtyKFjL9CDtNdCMm+R4924r0cjWXvSiNu7TALJx+OVwjzBl9yLuRjEZ8vWeDZ9oDlZjprSh9XUu9BdKjCyxLSigfGXwkf/BeP25MI5zp4KoWqLA+B9pstfjfgMU6CWOgrq2ZVybh3y3BB0saxeIG3E2NLqk2ONZhlIZE4sRufFS7eFhhUOW1RS1MPkOMy+n5ovq+xU/uLI8ib/XwZjzC6WJzIlBZVt0xUV9/dBGQxSQkNrgO2sHc9cC7cRQ4azKlMPTmut/w==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=PfQx6hs8RZD43KLx5G89DyOp6mys9dI8nirxO5KRbvDwlTRzOQx6uZhmNZeahBwzSdCxMw0rdkDWiBgWV509/Hq+UnSuWvvm5Zqm0jlec2XLsmNIwIbSyFr3ECSi542vwPfuyCCGhmhMQvftFj0nAKNF8r/9/oVCM3KQAWwDpaXLByZ1LWBABQ+d0vnWS2Eg6Xc+8xVj7f2NQHzrp1bY6jHkBeQL41IcRuXHdrtl//QUGPvHTR1GXimzjMeCod5TxlNB/1l9OzdvWiY93qLrfTq68HRu6xqpfWkNMoQGQmfAUFvXtp/CoaRGf1PW2MlqWYjriXo4vwKvKdrDRBN5pQ==
  • Delivered-to: jetty-users@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/jetty-users/>
  • List-help: <mailto:jetty-users-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=unsubscribe>
  • Thread-index: AQHY9Ghs/kXpTHwkrUqN86vWo3WTQa43BFG2//+tJICAAF/sAP//rg+AgABU2QD//629AA==
  • Thread-topic: [jetty-users] Jetty 12 schedule?
  • User-agent: Microsoft-MacOutlook/16.66.22102801
>    Scott, I'm not understanding how your facades work or why exactly
> they are needed?  Can you give some examples?

We have a deeply modular Spring-based system, where beans very "high" up need access to request/response state. The only practical way to inject the per-request interfaces into various objects is to use thread-local storage to capture and stash the current Servlet request/response and then inject a façade that pulls the thread-local copy out and delegates the method calls to it.

This is, among other things, a way to allow Spring ot instantiate components from third-party libraries that depend on Servlet APIs.

It's not to say we can't come up with other ways, but it's very widespread in our current design.

> Why can you not just deploy old javax. * code to one context and new
> jakarta. * code to a different one.

You're focused on javax/jakarta but that's not the issue. We already ported to jakarta. Both Servlet 5 and 6 are jakarta. The problem is they're not the same/compatible API, there are breaking changes in 6 removing deprecated methods that have been around a while.

-- Scott

Back to the top