Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 68298 invoked from network); 22 Aug 2005 18:54:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Aug 2005 18:54:19 -0000 Received: (qmail 62089 invoked by uid 500); 22 Aug 2005 18:54:16 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 62064 invoked by uid 500); 22 Aug 2005 18:54:16 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 62051 invoked by uid 99); 22 Aug 2005 18:54:15 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Aug 2005 11:54:15 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of pramod.immaneni@gmail.com designates 64.233.184.201 as permitted sender) Received: from [64.233.184.201] (HELO wproxy.gmail.com) (64.233.184.201) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Aug 2005 11:54:33 -0700 Received: by wproxy.gmail.com with SMTP id i24so927805wra for ; Mon, 22 Aug 2005 11:54:12 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=a/LY2ZPcaqlua0trwwG52Me0PrRKF+Rg6WuDXbYkbRlq3NpUnADT6Zr7/+w4/rxM0IqU8TXwq7965ML0NEx8P0uH02GjeUq3KbLSv4p+MkQ9zej0SxDx8aBzFO8RdYwUOAE2h9RUMPphgphNFrCiZ2BtC16IvWLEidGYtrDdXBM= Received: by 10.54.123.17 with SMTP id v17mr1625454wrc; Mon, 22 Aug 2005 11:54:11 -0700 (PDT) Received: by 10.54.141.9 with HTTP; Mon, 22 Aug 2005 11:54:11 -0700 (PDT) Message-ID: Date: Mon, 22 Aug 2005 11:54:11 -0700 From: Pramod Immaneni To: axis-dev@ws.apache.org Subject: Re: [jira] Commented: (AXIS-2171) same xml type java superclass registering serializer In-Reply-To: <1666583884.1124693048295.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1666583884.1124693048295.JavaMail.jira@ajax.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Will do that and let you know Srinivas. Will ant all-tests output errors on the screen if something is broken? Thanks. On 8/21/05, Davanum Srinivas (JIRA) wrote: > [ http://issues.apache.org/jira/browse/AXIS-2171?page=3Dcomments#actio= n_12319548 ] >=20 > Davanum Srinivas commented on AXIS-2171: > ---------------------------------------- >=20 > Pramod, >=20 > could you please try this with latest CVS. specifically run "ant clean al= l-tests" and make sure that nothing is broken. >=20 > -- dims >=20 > > same xml type java superclass registering serializer > > ---------------------------------------------------- > > > > Key: AXIS-2171 > > URL: http://issues.apache.org/jira/browse/AXIS-2171 > > Project: Apache Axis > > Type: Improvement > > Components: Serialization/Deserialization > > Versions: 1.2.1 > > Reporter: Pramod Immaneni > > Priority: Minor > > Attachments: patch_same_type_java_superclass-1_2_1 > > > > I was using axis and I needed to register a custom serializer for a > > java type with the following condition. The method signature has a > > return type of the java type but at runtime the method would return > > any implementation of this java type. > > So for example I have a method which is declared as following in the we= bservice > > IfaceA myMethod( myArgs ) > > and at runtime the method returns a ImplA which implements IfaceA. > > Since I am only interested in the IfaceA properties of the return > > object as declared in the webservice and may not know the > > implementation I would like to be able to register a serializer for > > IfaceA. > > In the 1.2.1 version I had to register the serializer for the > > implementation as well as the interface to get it to work. Attached > > is a patch that will allow one to just register a serializer for the > > interface and it will be picked up if one isnt found for the > > implementation (also as far as I could tell from the fix the > > serializer will not be picked up if the method returns the > > implementation instead of the interface which should be the right > > behaviour). >=20 > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the administrators: > http://issues.apache.org/jira/secure/Administrators.jspa > - > For more information on JIRA, see: > http://www.atlassian.com/software/jira >=20 >