Return-Path: X-Original-To: apmail-tomcat-dev-archive@www.apache.org Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0E6E1C7E6 for ; Tue, 4 Jun 2013 05:55:35 +0000 (UTC) Received: (qmail 62657 invoked by uid 500); 4 Jun 2013 05:55:33 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 62483 invoked by uid 500); 4 Jun 2013 05:55:33 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 62474 invoked by uid 99); 4 Jun 2013 05:55:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Jun 2013 05:55:32 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of nickytd@gmail.com designates 74.125.82.171 as permitted sender) Received: from [74.125.82.171] (HELO mail-we0-f171.google.com) (74.125.82.171) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Jun 2013 05:55:25 +0000 Received: by mail-we0-f171.google.com with SMTP id m46so2403967wev.2 for ; Mon, 03 Jun 2013 22:55:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=j5oGjow1Bu5Zi0W/L2dDXTDpFH4Okh6rjDwaWDllCEs=; b=bet6f+JeCaXDvbhEC6yTK3bdTUgtYrdTZQJ0tRe8D0mCeZ970O2sd3/c3Q33gTdwsH 281yGaRAcvUSsWvUG3+S+ABLiUJBU+faWUWrYWCvQLMwTe8e+5fsLeb/+q4XunpfKwby TxoBiIYBCFcYG2I1LslSWyM5xwcND/qBD8Gww8g9jfcUPdlcC4r2w66zBDF/MsQU3X4m HrNl1n1sldOFJObMA84EfkrEC405OjXAS9kMQjyjuvoIhwMwCZ3UMuDuwh2fqT+fNHnm sUoGopHoeWj8prihecOZATMd46SS5rqoG7JsXmxkw82BXUE1Z7kftwsRvOhqYXAi7eJk Fbyw== MIME-Version: 1.0 X-Received: by 10.180.9.195 with SMTP id c3mr1054520wib.61.1370325305450; Mon, 03 Jun 2013 22:55:05 -0700 (PDT) Received: by 10.180.182.232 with HTTP; Mon, 3 Jun 2013 22:55:05 -0700 (PDT) In-Reply-To: References: Date: Tue, 4 Jun 2013 08:55:05 +0300 Message-ID: Subject: Re: [Bug 55006] Add http proxy support for ClientEndpoint using system properties From: Niki Dokovski To: Tomcat Developers List Content-Type: multipart/alternative; boundary=001a11c244140ee7fc04de4db901 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c244140ee7fc04de4db901 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Jun 4, 2013 at 12:01 AM, Rossen Stoyanchev < rstoyanchev@gopivotal.com> wrote: > On Mon, Jun 3, 2013 at 10:27 AM, Niki Dokovski wrote: > > > On Mon, Jun 3, 2013 at 3:44 PM, Niki Dokovski > wrote:Further > > on, if you choose to use connectToServer call that has the > > ClientEndpointConfig param you are losing the annotation approach as the > > first param of this call has to be an instance of an Endpoint. Hence your > > class can not be just annotated. hmmm Mark where can we bring this > > discussion? > > > This is not very obvious from the API but ClientEndpointConfig (and > ServerEndpointConfig) are not meant to be used with annotated endpoints. In > other words, I think the methods accepting those types are for use with > type-based endpoints (i.e. javax.websocket.Endpoint). So as far as I can > see user properties can be updated before the session starts only for > type-based endpoints. > Exactly, What is the rationale behind this? Still an annotated endpoint can supply javax.websocket.ClientEndpointConfig.Configurator but has no access to the user properties from there. May be the javax.websocket.ClientEndpointConfig.Configurator can be extended to provide access to the map. cheers > > Rossen > --001a11c244140ee7fc04de4db901--