I disagree. MVC - A SOAP client requester is just another V, why wouldn't you want to reuse the M and C? I see very little difference between a SOAP response and a Struts response in XML/XSLT. I for one do not want more than one set of Business Logic components on my Data Model, regardless of the source of the Request. I also see very little difference between a SOAP Request with a serialized FormBean in it and an html form post, except of course the format of the inputstream. The content, which is what matters, would be the same.
I would not modify the ActionServlet, but I would have an Axis/SOAP entry point that did similar work and reused the Struts components alongside the ActionServlet as an alternate entry point. That means a request from either a user on a web browser posting a form or doing a get would execute the same RequestHandler, access the same Data Model and business logic and get a response from a Forward that formed a SOAP Response instead of a web page. Michael Oliver AppsAsPeers LLC 7391 S. Bullrider Ave. Tucson, AZ 85747 Phone:(520)574-1150 Fax:(520)844-1036 -----Original Message----- From: Bradley G Smith [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 9:46 AM To: Struts Users Mailing List Subject: Re: Axis/SOAP proposal for Struts I have been thinking about it this off and on for a while. It seems to me that SOAP (or xml-rpc or ...) would be another access point into the business logic of the application that is a peer to the access point provided by a Struts-based layer. The Struts-based components provide the mechanism to deliver content to web browsers, the SOAP interface enables content delivery from the business logic layer to other types of clients on the network. I do not see the need to extend the ActionServlet to provide this type of access. Brad Smith "Mike Oliver" <ollie@appsaspee To: <[EMAIL PROTECTED]> rs.com> cc: Subject: Axis/SOAP proposal for Struts 17-01-03 07:45 Please respond to "Struts Users Mailing List" Struts Users, I would like to propose that Struts be extended to support another entry point. The ActionServlet would be augmented by an Axis/SOAP Web Services Interface to Struts. FormBeans would be part of the payload for requests. Responses would be generated by Forwards for SOAP. This new Axis entry point would do the same work as ActionServlet with the only significant difference being the construction of the FormBean. Incoming SOAP Requests would be configured to call the same RequestHandlers and as far as the actions go they won't know that the source was an HTML Form or a serialized FormBean. I feel this will give a great deal of flexibility to Applications where they want a Web Browser User Interface as well as Web Services for the same Application Data Model and Business Logic. I am planning on doing this anyway, and felt it applicable to this group and would offer to share it as a sub project and would welcome contributions of thought, expertise and code. Michael Oliver Chief Technology Officer AppsAsPeers LLC 7391 S. Bullrider Ave. Tucson, AZ 85747 520.574.1150 Voice 520.844.1036 Fax 520.270.8862 Cell http://www.appsaspeers.com <http://www.appsaspeers.com/> Home Page [EMAIL PROTECTED] SMS http://www.ollie.ezpeer.net <http://www.ollie.ezpeer.net/> Personal Home Page http://www.ollie.im-live.com/im-live/ Instant Chat [EMAIL PROTECTED] MSN Messenger [EMAIL PROTECTED] Yahoo Instant Messenger MikeOliverAZ Aol Instant Messenger -- 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]>
