Not over trivial at all, and could influence where we find the commonality. If this works out, we may offer other Struts entry points for various transports with equal ease. Certainly one of the advantages of an Axis4Struts layer could be that "if it works for Axis it works for Struts" and I think that should be part of the design criteria.
Michael Oliver AppsAsPeers LLC 7391 S. Bullrider Ave. Tucson, AZ 85747 Phone:(520)574-1150 Fax:(520)844-1036 -----Original Message----- From: Will Etson [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 1:48 PM To: [EMAIL PROTECTED] Subject: RE: Axis/SOAP proposal for Struts Not to quibble over trivialities, but SOAP is a transport independent payload and is not dependant on HTTPRequest and HTTPResponse. Axis supports this notion very well. How this would effect the integration of the two technologies, I can't say. Will Etson >>> "Mike Oliver" <[EMAIL PROTECTED]> 01/17/03 10:31AM >>> There certainly are some bugaboos in the marriage of these two technologies (Axis/Struts) but I don't think them to be insurmountable. For example the dependency on the HTTPRequest and HTTPResponse, a SOAP Request is after all an HTTP request. So the problem becomes more the difference in the format of the input and output streams, eh? My hope is that we can find a fairly clear line of commonality and my gut feel is that the commonality line between the two entry points merge at the call to the RequestHandler, but perhaps it is one level below that with a SOAPRequestHandler that calls Actions and the Actions are common. Michael Oliver AppsAsPeers LLC 7391 S. Bullrider Ave. Tucson, AZ 85747 Phone:(520)574-1150 Fax:(520)844-1036 -----Original Message----- From: Joe Germuska [ mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 10:29 AM To: Struts Users Mailing List Subject: RE: Axis/SOAP proposal for Struts At 11:02 AM -0500 2003/01/17, Mark Galbreath wrote: >I actually AM doing this now, but I whole-heartedly agree that a >standardized Axis/SOAP interface to Struts would be very, very cool. > At 9:54 AM -0700 2003/01/17, Mike Oliver wrote: >The nice thing would be to do it now, for 1.1 outside the current >stream, but get a dialog going so the work done for it can be used at >least for lessons learned when the effort for 2.0 begins. Mark: care to elaborate on the big picture design you're using? Mike: have you got a design vision? I have to admit that I'm having some trouble seeing how to fit it in to Struts 1.x when the actions depend on HTTP request and response, but then, I haven't spent much time thinking about it. Joe -- -- Joe Germuska | "Big corporations here now believe we will have war. [EMAIL PROTECTED] | Believe all would welcome it as relief to suspense." http://blog.germuska.com/ | telegram to President McKinley, 25 March 1898 -- To unsubscribe, e-mail: < mailto:[EMAIL PROTECTED] > For additional commands, e-mail: < mailto:[EMAIL PROTECTED] > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
