Return-Path: Delivered-To: apmail-incubator-beehive-dev-archive@www.apache.org Received: (qmail 5720 invoked from network); 11 Jun 2005 02:15:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 11 Jun 2005 02:15:52 -0000 Received: (qmail 73275 invoked by uid 500); 11 Jun 2005 02:15:52 -0000 Delivered-To: apmail-incubator-beehive-dev-archive@incubator.apache.org Received: (qmail 73249 invoked by uid 500); 11 Jun 2005 02:15:51 -0000 Mailing-List: contact beehive-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Beehive Developers" Delivered-To: mailing list beehive-dev@incubator.apache.org Received: (qmail 73233 invoked by uid 99); 11 Jun 2005 02:15:51 -0000 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=HTML_20_30,HTML_MESSAGE,RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of chad.schoettger@gmail.com designates 64.233.162.199 as permitted sender) Received: from zproxy.gmail.com (HELO zproxy.gmail.com) (64.233.162.199) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 10 Jun 2005 19:15:48 -0700 Received: by zproxy.gmail.com with SMTP id 40so1084727nzk for ; Fri, 10 Jun 2005 19:15:46 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references; b=FI4KtCS1wMtNQkRTUSTtaBGmrLNSuMvxz+F/jK6ie07RtFZWgaDO/Xs7wtp553w3hGpHSm/731gTfJI0JTK8jfli17dom72c4d7O+qqDM0NnTumZcqpBYQWUhYmxyjsJ54yxAzpYeBgSCc0Cvb+IUFbgJoVu3AE11Hwbb1LMC5g= Received: by 10.36.104.3 with SMTP id b3mr1557593nzc; Fri, 10 Jun 2005 19:15:45 -0700 (PDT) Received: by 10.36.34.5 with HTTP; Fri, 10 Jun 2005 19:15:45 -0700 (PDT) Message-ID: Date: Fri, 10 Jun 2005 20:15:45 -0600 From: Chad Schoettger Reply-To: Chad Schoettger To: Daryoush Mehrtash , Beehive Developers Subject: Re: Service Control generation question.... In-Reply-To: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_6431_7452752.1118456145916" References: <4B2B4C417991364996F035E1EE39E2E103086A72@uskiex01.bea.com> X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_6431_7452752.1118456145916 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sure, I'll file a bug on this issue. I'm still a bit curious as to why the method signature generated by the=20 ExtensionMaker is: public void=20 UpdatePhoneNumbers( org.apache.beehive.wsm.databinding.GenericHolder=20 address1, web.webparam.Phone phone, javax.xml.rpc.holders.IntHolder return,=20 org.apache.beehive.wsm.databinding.GenericHolderaddre= ss2)=20 throws Exception; INSTEAD OF: public int=20 UpdatePhoneNumbers( org.apache.beehive.wsm.databinding.GenericHolder=20 address1, org.apache.beehive.wsm.databinding.GenericHolderaddre= ss2)=20 throws Exception; It seems the second form would be a more accurate representation of the=20 webservice call than the first. But perhaps there is some technical reason= =20 for this?=20 - Chad On 6/10/05, Daryoush Mehrtash wrote: >=20 > I don't discount the use of headers, in fact last time I checked EBay > does use it for it authentication.. As you pointed out Header makes a > lot of sense for things like Authentication, transaction mgmt, etc. > But if you were to implement these services you would implement them > using a Handler as oppose to arguments on the methods, very similar to > the EJB model were the beans are not involved in security or > transaction aspects of the call. >=20 > Lets say you want to have a security header parameter that is your > message checksum, at the time the JWS methods is called there is no > message for you to checksum, you would have to have a handler to get > the outgoing message (or incoming) to generate (or validate) the > checksum. So having the checksum as an argument to the methods wont > make any sense. Something with transaction you want that handled > outside the method call. >=20 > The 181 spec does require header=3Dtrue, which means we do have to > implement it on the server side. But I don't believe this will be a > common use case and I question the priority of this test on the > service control compare to other tests we could be developing. >=20 > Daryoush >=20 >=20 >=20 > On 6/10/05, Jacob Danner wrote: > > Just to chime in here on top of my last 181 post. > > > > "I am curious to know why you think having INOUT parameters in the > > Header would be useful." > > > > The soap spec says the following about SOAP Headers (4.2): > > SOAP provides a flexible mechanism for extending a message in a > > decentralized and modular way without prior knowledge between the > > communicating parties. Typical examples of extensions that can be > > implemented as header entries are authentication, transaction > > management, payment etc. > > > > So using Headers allows for future extensions. With WS being relatively > > new, the possibilities are endless. > > I don't think it's feasible at this early in the game to say that using > > an INOUT header doesn't make sense only because few standards really > > make use of it at this point. There are many standards still in draft > > and being developed that may make use of information in the header. We > > shouldn't discount it soo soon. > > -Jacobd > > > > > > -----Original Message----- > > From: Daryoush Mehrtash > > Sent: Friday, June 10, 2005 1:05 PM > > To: Chad Schoettger; Beehive Developers > > Subject: RE: Service Control generation question.... > > > > I haven't looked at this, but I do have a question, (and this may not > > have anything to do with the problem you are having) why are you puttin= g > > INOUT parameters in Header? This is an area were we do have known > > issues (I believe there are two bugs already filed on this) also I > > can't imagine this case being a realistic usage scenario. I am curious > > to know why you think having INOUT parameters in the Header would be > > useful. > > > > Does the test work if the parameters were not in the header? > > > > Daryoush > > > > > -----Original Message----- > > > From: Chad Schoettger [mailto:chad.schoettger@gmail.com] > > > Sent: Friday, June 10, 2005 12:52 PM > > > To: Beehive Developers; Daryoush Mehrtash > > > Subject: Service Control generation question.... > > > > > > So I'm working some new drt's for the webservice system control and > > > have run into a bug but I'm not sure how to classify it: > > > > > > It occurs when I try to generate a service control from the > > > wsm-samples/webparams webservice's wsdl. > > > > > > > > > The annotated web service method is: > > > > > -----------------------------------------------------------------------= - > > -- > > > ------------------- > > > @WebMethod > > > public int updatePhoneNumbers( > > > Phone phone, > > > @WebParam(name=3D"address1", header=3Dtrue, > > > mode=3DWebParam.Mode.INOUT) AddressHolder addressHolder1, > > > @WebParam(name=3D"address2", header=3Dtrue, > > > mode=3DWebParam.Mode.OUT) AddressHolder addressHolder2 > > > ) { .... } > > > > > -----------------------------------------------------------------------= - > > -- > > > ---------------------- > > > > > > The WSDL is attached. > > > > > > The generated webservice control method is: > > > > > -----------------------------------------------------------------------= - > > -- > > > --------------------- > > > public void > > > > > UpdatePhoneNumbers(org.apache.beehive.wsm.databinding.GenericHolder > we > > > bparam.Address> > > > address1, web.webparam.Phone phone, javax.xml.rpc.holders.IntHolder > > > return, > > > org.apache.beehive.wsm.databinding.GenericHolder > > > address2) throws Exception; > > > > > -----------------------------------------------------------------------= - > > -- > > > --------------------- > > > > > > When the generated webservice control is compiled, apt blows up due t= o > > > the 'return' parameter name in the arg list. > > > > > > Questions: > > > > > > 1) Is the control method being generated correctly? Should the > > > 'return' parameter be the return value for the generated method? like= : > > > > > > public int > > > > > UpdatePhoneNumbers(org.apache.beehive.wsm.databinding.GenericHolder > we > > > bparam.Address> > > > address1, web.webparam.Phone phone, > > > org.apache.beehive.wsm.databinding.GenericHolder > > > address2) throws Exception; > > > > > > > > > 2) If the method is being generated correctly - it seems the proper > > > fix would be to modify the ExtensionGenerator class to check for para= m > > > names which are Java keywords and modify them to non-keywords so that > > > the control can be compiled. Or would the proper fix be to modify the > > > wsm model to correctly 'encode' the param as a non-java keyword? > > > > > > Thanks for any input on this. Once I have determined where the fix > > > needs to be made I will file a bug. > > > > > > -----------------------------------------------------------------------= - > > -------- > > > > Join CEO Alfred Chuang and CTO Mark Carges on June 15 for a unique > > online > > event, giving you the first look at a new category of enterprise > > software > > built specifically for Service-Oriented Architecture (SOA). > > > > Register Now. It's Free! > > > > http://www.bea.com/events/june15 > > > >=20 > -------------------------------------------------------------------------= ------- > > > > Join CEO Alfred Chuang and CTO Mark Carges on June 15 for a unique=20 > online > > event, giving you the first look at a new category of enterprise=20 > software > > built specifically for Service-Oriented Architecture (SOA). > > > > Register Now. It's Free! > > > > http://www.bea.com/events/june15 > > >=20 >=20 > -- > Daryoush >=20 > Weblog: http://perlustration.blogspot.com/ > ------=_Part_6431_7452752.1118456145916--