Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 63014 invoked from network); 22 Feb 2007 21:22:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Feb 2007 21:22:11 -0000 Received: (qmail 2443 invoked by uid 500); 22 Feb 2007 21:22:16 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 2397 invoked by uid 500); 22 Feb 2007 21:22: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 2385 invoked by uid 99); 22 Feb 2007 21:22:15 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Feb 2007 13:22:15 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of davanum@gmail.com designates 66.249.92.175 as permitted sender) Received: from [66.249.92.175] (HELO ug-out-1314.google.com) (66.249.92.175) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Feb 2007 13:22:05 -0800 Received: by ug-out-1314.google.com with SMTP id j40so227284ugd for ; Thu, 22 Feb 2007 13:21:44 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=KUSRp6e445bffgfj+AV6QnV5PZEUwZcAYXjaK+e9vAca8Wbuomo8j3LpjhXa2x4f+VlQueN5I9Ip41A+5BE+5hPOJH5mzI6EiyY6h9bEQkIZ4o5cArSeZ5xPaEVeSfVKo0YNu+4FBwSk7FOFgyTj6l0wtEYRPSFcmayyraZCqpo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qIBN007NheaKMuj074OWRQSTXOg+ngWCaFo5rgTqdxR8NntPUK6o5d7j0AwTpIHsulwQjzP4xXR0C4Etu3NQrqmjfQRn/7e95M+i88NBf9lPMFaYI/zYI1Q0IuMQiZkcqYrJfjIQhtUyv4JFsdS9pfrA//S6L81977C+jqGqgzo= Received: by 10.114.200.2 with SMTP id x2mr503614waf.1172179303419; Thu, 22 Feb 2007 13:21:43 -0800 (PST) Received: by 10.115.94.1 with HTTP; Thu, 22 Feb 2007 13:21:43 -0800 (PST) Message-ID: <19e0530f0702221321l627eb806uca8a4aace22fffe0@mail.gmail.com> Date: Thu, 22 Feb 2007 16:21:43 -0500 From: "Davanum Srinivas" Reply-To: dims@apache.org To: axis-dev@ws.apache.org Subject: Re: [Axis2] POJO annotation 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: <45DD5039.8070107@opensource.lk> X-Virus-Checked: Checked by ClamAV on apache.org Jeff, So instead of calling ServiceDescription sd = DescriptionFactory.createServiceDescriptionFromServiceImpl(myClazz, myAxisService) configCtx.getAxisConfiguration().addService(myAxisService); We should do the following? JavaClassToDBCConverter converter = new JavaClassToDBCConverter(myClazz); HashMap dbcMap = converter.produceDBC(); List serviceDescList = DescriptionFactory.createServiceDescriptionFromDBCMap(dbcMap); EndpointDescription[] edArray = serviceDescList.get(0).getEndpointDescriptions(); AxisService service = ed[0].getAxisService(): configCtx.getAxisConfiguration().addService(myAxisService); In other words, how do we get a fully configured AxisService from a given class? :) thanks, dims On 2/22/07, Jeff Barrett wrote: > Hi Deepal, > > You may not have seen it yet, but I replied yesterday to your note on not > getting the AxisOperations when you used the metadata layer. I believe > that had to do with which DescriptionFactory method you were using. I'm > just about to commit updates to the javadoc in that class and tagging the > method you were using as deprecated. Sorry the javadoc wasn't better in > there to begin with! > > The metadata module will build up the full AxisService description > hierachy given just annotations (no WSDL), or annotations and WSDL. > Currently the metadata layer does NOT generate the correct schema if > there's no WSDL; that is something it should probably do. > > Other than that, if the POJODeployer were to create a > DescriptionBuilderComposite (using the JavaReflection to DBC converter in > the metadata package, at least for now), it should be able to use the > metadata layer for both the WSDL-provided and no-WSDL-provided/annotations > only case. > > Thanks, > Jeff > > IBM Software Group - WebSphere Web Services Development > Phone: 512-838-4587 or Tie Line 678-4587 > Internet e-mail and Sametime ID: barrettj@us.ibm.com > > > > Deepal Jayasinghe > 02/22/2007 02:11 AM > Please respond to > axis-dev@ws.apache.org > > > To > "axis-dev@ws.apache.org" > cc > > Subject > [Axis2] POJO annotation > > > > > > > Hi all; > > As I mentioned before last few days I was working on POJO annotation > support and there I was thinking to use matadata and jaxws module to > have this feature. When I start implementing annotation support I found > that the created AxisService from metadata module does not have any > operation in it (though I have annotated the service impl class > correctly). > > In the meantime I had a big issue in Java2WSDL support when annotation > present in the POJO , the only option was to re-write or duplicate > ScheamGenerator logic. And I realized that going to be a big code change > so what I did was, use JAM (annogen) to have annotation support in > SchemaGenerator. > > With the above I have implemented pojo annotation support in axis2. So I > have written a Deployer called POJODeployer and you can deploy POJO as > .class file and it will make that to an AxisService and will generate > correct schema (so you will see the correct wsdl at the runtime). > > If the WebService has wsdllocation annotation then it will call metadata > module to create AxisService (this path has few TODO items) > > please comment on my implementation , and I will commit the code you can > go though that and find out if I have done something wrong. > > P.S:- Implementation is not completed yet need few more items to complete. > > Thanks > Deepal > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-dev-help@ws.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-dev-help@ws.apache.org > > -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers --------------------------------------------------------------------- To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-dev-help@ws.apache.org