Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 80815 invoked from network); 27 Nov 2006 15:45:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Nov 2006 15:45:50 -0000 Received: (qmail 97063 invoked by uid 500); 27 Nov 2006 15:45:56 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 97025 invoked by uid 500); 27 Nov 2006 15:45:55 -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 97014 invoked by uid 99); 27 Nov 2006 15:45:55 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Nov 2006 07:45:55 -0800 X-ASF-Spam-Status: No, hits=2.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of nlgallar@us.ibm.com designates 32.97.110.152 as permitted sender) Received: from [32.97.110.152] (HELO e34.co.us.ibm.com) (32.97.110.152) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Nov 2006 07:45:42 -0800 Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e34.co.us.ibm.com (8.13.8/8.12.11) with ESMTP id kARFjMpg004166 for ; Mon, 27 Nov 2006 10:45:22 -0500 Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by westrelay02.boulder.ibm.com (8.13.6/8.13.6/NCO v8.1.1) with ESMTP id kARFjLZp503606 for ; Mon, 27 Nov 2006 08:45:21 -0700 Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id kARFjL7v018255 for ; Mon, 27 Nov 2006 08:45:21 -0700 Received: from d03nm118.boulder.ibm.com (d03nm118.boulder.ibm.com [9.17.195.144]) by d03av03.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id kARFjLLi018245 for ; Mon, 27 Nov 2006 08:45:21 -0700 In-Reply-To: <1163733917.16062.11.camel@localhost.localdomain> To: axis-dev@ws.apache.org Subject: Re: [Axis2][jaxws] deploying jsr 181 service MIME-Version: 1.0 X-Mailer: Lotus Notes Release 7.0 HF242 April 21, 2006 Message-ID: From: Nicholas L Gallardo Date: Mon, 27 Nov 2006 09:46:36 -0600 X-MIMETrack: Serialize by Router on D03NM118/03/M/IBM(Release 7.0.2HF32 | October 17, 2006) at 11/27/2006 08:46:37, Serialize complete at 11/27/2006 08:46:37 Content-Type: multipart/alternative; boundary="=_alternative 00568BB186257233_=" X-Virus-Checked: Checked by ClamAV on apache.org --=_alternative 00568BB186257233_= Content-Type: text/plain; charset="US-ASCII" Sanjiva, I agree with most of what you proposed there with the exception of the "beans" directory. It seems like that would be the same thing as creating a node under the "services" directory and just dropping the bean in there, correct? Or am I misunderstanding the intent? In the current deployment model, what happens if a user puts their service classes/config directly under the "services" directory rather than creating a sub-directory? Will that endpoint not be deployed at all? Regards, Nicholas Gallardo WebSphere - WebServices Development nlgallar@us.ibm.com Phone: 512-838-1182 Building: 901 / 5G-016 Sanjiva Weerawarana 11/16/2006 09:25 PM Please respond to axis-dev@ws.apache.org To dims@apache.org cc axis-dev@ws.apache.org Subject Re: [Axis2][jaxws] deploying jsr 181 service On Thu, 2006-11-16 at 19:14 -0500, Davanum Srinivas wrote: > Rajith, > > I went thru the patch, and i went thru the current code in JAXWS. So > it was a loaded question :) > > I think we need to define the simplest case. IMHO, the simplest > deployment case should work exactly like our RPC*MessageReceiver. > > - User writes a services.xml > - Specifies say Jsr181MessageReceiver as the MR > - Specifies a class with a @WebService as the ServiceClass I'd prefer the simple case to be: - User writes a class, jars it up and deploys the jar (yes a regular jar, not an aar) - We look for the Main-Class attribute in the manifest to see whether there's a class identified, if not we consider every class a candidate for the next step - Look for @WebService annotations on the class and deploy those classes as services I'd also like to support the ultra simple case of a single .class that needs to be deployed. So what I'm saying is add say a "beans/" directory to the repository and look for jar and .class files there and do the above. > Don't want any listeners/notifications/peeking-thru-the-jars. > basically KISS [1]. Do you have some cycles to help with this? This is as KISS as you can do legally IMO. Sanjiva. --------------------------------------------------------------------- To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-dev-help@ws.apache.org --=_alternative 00568BB186257233_= Content-Type: text/html; charset="US-ASCII"
Sanjiva,

I agree with most of what you proposed there with the exception of the "beans" directory.  It seems like that would be the same thing as creating a node under the "services" directory and just dropping the bean in there, correct?  Or am I misunderstanding the intent?

In the current deployment model, what happens if a user puts their service classes/config directly under the "services" directory rather than creating a sub-directory?  Will that endpoint not be deployed at all?

Regards,

Nicholas Gallardo
WebSphere  -  WebServices Development
nlgallar@us.ibm.com
Phone: 512-838-1182
Building: 901 / 5G-016


Sanjiva Weerawarana <sanjiva@opensource.lk>

11/16/2006 09:25 PM
Please respond to
axis-dev@ws.apache.org
To
dims@apache.org
cc
axis-dev@ws.apache.org
Subject
Re: [Axis2][jaxws] deploying jsr 181 service





On Thu, 2006-11-16 at 19:14 -0500, Davanum Srinivas wrote:
> Rajith,
>
> I went thru the patch, and i went thru the current code in JAXWS. So
> it was a loaded question :)
>
> I think we need to define the simplest case. IMHO, the simplest
> deployment case should work exactly like our RPC*MessageReceiver.
>
> - User writes a services.xml
> - Specifies say Jsr181MessageReceiver as the MR
> - Specifies a class with a @WebService as the ServiceClass

I'd prefer the simple case to be:

- User writes a class, jars it up and deploys the jar (yes a regular
jar, not an aar)
- We look for the Main-Class attribute in the manifest to see whether
there's a class identified, if not we consider every class a candidate
for the next step
- Look for @WebService annotations on the class and deploy those classes
as services

I'd also like to support the ultra simple case of a single .class that
needs to be deployed. So what I'm saying is add say a "beans/" directory
to the repository and look for jar and .class files there and do the
above.

> Don't want any listeners/notifications/peeking-thru-the-jars.
> basically KISS [1]. Do you have some cycles to help with this?

This is as KISS as you can do legally IMO.

Sanjiva.



---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
--=_alternative 00568BB186257233_=--