Return-Path: X-Original-To: apmail-synapse-dev-archive@www.apache.org Delivered-To: apmail-synapse-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 DDD2195E4 for ; Mon, 19 Mar 2012 08:45:17 +0000 (UTC) Received: (qmail 65546 invoked by uid 500); 19 Mar 2012 08:45:17 -0000 Delivered-To: apmail-synapse-dev-archive@synapse.apache.org Received: (qmail 65324 invoked by uid 500); 19 Mar 2012 08:45:15 -0000 Mailing-List: contact dev-help@synapse.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@synapse.apache.org Delivered-To: mailing list dev@synapse.apache.org Received: (qmail 65296 invoked by uid 99); 19 Mar 2012 08:45:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Mar 2012 08:45:14 +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 (athena.apache.org: domain of afkham@gmail.com designates 74.125.82.170 as permitted sender) Received: from [74.125.82.170] (HELO mail-we0-f170.google.com) (74.125.82.170) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Mar 2012 08:45:07 +0000 Received: by werh12 with SMTP id h12so6140491wer.15 for ; Mon, 19 Mar 2012 01:44:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=AFblbXljHEnztDev/VTmwsqs1Hk2hxVDGAMlem0lnWg=; b=iTuf0AaYrGGaABnV2ktNY0HCF+lCQZWZE54U4/Tev4fEuxBVacubqaAaEaIkVwiLrJ 7iTm48RQudK6tm5Edxa/zngTXC4luVS63/mHDiavaiNfi5uhADG+j2e3MjQlPb9P1P/L WHj1iQaBANImL0kBqfV/lBWpfSqzTaTiXje9IHA1n45idrwNVx7RNkvVXGZA6YPKC5W2 1HIqMD8Stw6yPIzM3MN24rHe1BbA//O+xFM7vCJEp5jF6j+uNYV3A+rxgV5+StNU9Gcu tMh7JZjDVA+Arg2ElLN7XMUkwOxMRLlvH8zjf0o64Y2/VjAfE+oSzVrR7X0EqUbMUItC K9/Q== Received: by 10.180.102.129 with SMTP id fo1mr17879689wib.6.1332146686574; Mon, 19 Mar 2012 01:44:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.102.97 with HTTP; Mon, 19 Mar 2012 01:44:26 -0700 (PDT) In-Reply-To: References: From: Afkham Azeez Date: Mon, 19 Mar 2012 14:14:26 +0530 Message-ID: Subject: Re: Serilaizer for custom endpoint implementation.. To: dev@synapse.apache.org Content-Type: multipart/alternative; boundary=f46d044481490abee004bb9492db X-Virus-Checked: Checked by ClamAV on apache.org --f46d044481490abee004bb9492db Content-Type: text/plain; charset=ISO-8859-1 Yes, I didn't implement the serialization part. However, custom endpoint definition is working fine. The tricky thing is, the serialization logic does an "instanceof" check on the endpoint type, and then tries to serialize it. So, serialization does not work for any endpoint we define using class endpoint. We have to think of a proper way to implement this. On Mon, Mar 19, 2012 at 1:57 PM, vijayaratha vijayasingam < vijayaratha@gmail.com> wrote: > Hi azeez, > I tried the recent implementation of supporting the custom endpoints, but > facing an issue while saving the custom endpoints..No Serializer for this > type endpoint? > > Thanks > -Ratha > --f46d044481490abee004bb9492db Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Yes, I didn't implement the serialization part. However, custom endpoin= t definition is working fine. The tricky thing is, the serialization logic = does an "instanceof" check on the endpoint type, and then tries t= o serialize it. So, serialization does not work for any endpoint we define = using class endpoint. We have to think of a proper way to implement this.
On Mon, Mar 19, 2012 at 1:57 PM, vijayaratha= vijayasingam <vijayaratha@gmail.com> wrote:
= Hi azeez,
I tried the recent implementation of supporting=A0 the custom endpoints,=20 but facing an issue while saving the custom endpoints..No Serializer for this type endpoint?

Thanks
-Ratha
=

--f46d044481490abee004bb9492db--