Return-Path: Delivered-To: apmail-beehive-dev-archive@www.apache.org Received: (qmail 59353 invoked from network); 24 Jul 2006 04:43:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 24 Jul 2006 04:43:35 -0000 Received: (qmail 47853 invoked by uid 500); 24 Jul 2006 04:43:35 -0000 Delivered-To: apmail-beehive-dev-archive@beehive.apache.org Received: (qmail 47671 invoked by uid 500); 24 Jul 2006 04:43:35 -0000 Mailing-List: contact dev-help@beehive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Beehive Developers" Delivered-To: mailing list dev@beehive.apache.org Received: (qmail 47660 invoked by uid 99); 24 Jul 2006 04:43:35 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Jul 2006 21:43:35 -0700 X-ASF-Spam-Status: No, hits=0.8 required=10.0 tests=DNS_FROM_RFC_ABUSE,MAILTO_TO_SPAM_ADDR,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of ekoneil@gmail.com designates 64.233.182.184 as permitted sender) Received: from [64.233.182.184] (HELO nf-out-0910.google.com) (64.233.182.184) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Jul 2006 21:43:33 -0700 Received: by nf-out-0910.google.com with SMTP id y38so1314412nfb for ; Sun, 23 Jul 2006 21:43: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=ZJVybxN2WBflGAgq6suvzEJg9bqDkMZRoacGUKL0HxI1S+1XuLMa+9W0JiXq7WyH1adAd+od3c7BoSVhKHV4zu1QUOoUIyxA0rrDPx5ueSBGXeIDC3Gfpdbg9o/rsGxZIM5w4Mje7Lt2OSST7WRqoEfJmUPfQYHKKMBjhtr7YvM= Received: by 10.48.210.20 with SMTP id i20mr2973008nfg; Sun, 23 Jul 2006 21:43:12 -0700 (PDT) Received: by 10.48.254.18 with HTTP; Sun, 23 Jul 2006 21:43:12 -0700 (PDT) Message-ID: Date: Sun, 23 Jul 2006 22:43:12 -0600 From: "Eddie O'Neil" To: "Beehive Developers" Subject: Re: JSR 181 support for axis2 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N A'right -- mail is in legal-discuss@. Will be interesting to see how that conversation turns out. :) Interested parties should follow the discussion there. Eddie On 7/23/06, Eddie O'Neil wrote: > Rajith-- > > Hey -- something came up this weekend and I am just getting back to > this now. My gut is that this type of metadata modification to an API > class isn't going to fly (mail about this shortly); since the annogen > beans are just generated from the annotations themselves, can we just > hand code them to match the JSR-181 annotations? > > Will take a look at the patch... > > Eddie > > > > On 7/23/06, Rajith Attapattu wrote: > > Eddie, > > > > any update on the issue? > > > > Regards, > > > > Rajith > > > > On 7/20/06, Rajith Attapattu wrote: > > > > > > Eddie, > > > > > > I totally forgot about sending the patch, but finnaly did it today. > > > Please review it and let me know your comments. > > > > > > We still need to figure out the legal issue about adding an annotation to > > > the spec class. > > > (Does annogen have a way around without annotatiing the classes, for it to > > > generate the AnnoBean classes.???) > > > > > > > 2.) Generating Annogen beans for meta data > > > > The annogen task that generates code based on the annotated classes > > > > seems to have a bug with inner classes. > > > > For example WebParam.Mode gives compilation errors as it cannot the > > > > handle the inner class > > > > So I eidted the generated source file to get it working. (I maybe > > > wrong > > > > here...) > > > > > > > > > > This is still an issue :-( > > > > > > Regards, > > > > > > Rajith > > > > > > On 7/11/06, Rajith Attapattu wrote: > > > > > > > > Eddie, > > > > > > > > oops, didn't think it was that serious about modifying the spec classes. > > > > But can u please let me know about it. > > > > > > > > > > > > > > > > >[eko] Not sure I follow this -- let me take a look at it and I'll get > > > > >back to you. > > > > I didn't even submit the patch for this part. I will do so. > > > > Please take a look at it then. > > > > > > > > I am really gratefull for your assitance. > > > > > > > > Regards, > > > > > > > > Rajith > > > > > > > > > > > > On 7/11/06, Eddie O'Neil wrote: > > > > > > > > > > Rajith-- > > > > > > > > > > Comments on both of your questions below... > > > > > > > > > > Eddie > > > > > > > > > > > > > > > > > 1.) Annogen requires you to annotate the annotation classes with > > > > > the > > > > > > following annotation > > > > > > Now are we allowed to modifty the JSR api classes to add the above > > > > > lines of > > > > > > code ?? > > > > > > > > > > [eko] This is a *great* question :) and probably the first time > > > > > we've run into this at Apache. If you were asking to add a *method* > > > > > to a type described in a specification, the answer would be no because > > > > > > > > > > we can't change spec classes. Since it's metadata, I don't know the > > > > > answer -- my gut would be that we can't change the metadata on a > > > > > specification class, but it's a question worth asking legal@apache > > > > > just to see what folks think. > > > > > > > > > > > > > > > > 2.) Generating Annogen beans for meta data > > > > > > The annogen task that generates code based on the annotated > > > > > classes > > > > > > seems to have a bug with inner classes. > > > > > > For example WebParam.Mode gives compilation errors as it cannot > > > > > the > > > > > > handle the inner class > > > > > > So I eidted the generated source file to get it working. (I > > > > > maybe wrong > > > > > > here...) > > > > > > > > > > > > > > > > [eko] Not sure I follow this -- let me take a look at it and I'll get > > > > > back to you. > > > > > > > > > > > > > > > > > > > > >