And if you (or any of the Tucson JUG) want to contribute just let me know and I will add you in.
http://sourceforge.net/projects/axis4struts/ And Warner if you want to contribute you can take the task of creating a snazzy Home page for: http://axis4struts.sourceforge.net You will get a lot of exposure with that. One of the first topics of discussion is where the Axis4Struts entry point should be? I can see several possibilities: One would be to clone/extend the ActionServlet as it is the component in standard struts that calls the Module's RequestHandlers. The advantage here would be the same RequestHandler objects for Struts modules would be called getting reuse at that level. The problem there is that there is heavy dependency on the content and context of the HTTPRequest and HTTPResponse in the ActionServlet which means heavy lifting to translate the SOAPRequest and SOAPResponse payloads. Another would be to create a more common Java Object class that did much of the work of the ActionServlet and was the interface entry point for the Axis WSDL file and generated servlets entry point, and the source for the Axis Engine generation and that class would call a SOAP/Axis RequestHandler which would be a clone/extension of the standard Struts RequestHandler. This would make the Actions the common layer not the ActionServlet. The problem here is that with Struts 1.1 there are modules and if the standard Struts application has different RequestHandlers for different Modules, then you would probably need to clone each one of those into a ModuleSOAPRequestHandler, which complicates reuse. There are other possibilities such as AspectJ and even the use of Servlet Include and Forward of the SOAPRequest and SOAPResponse through a dispatcher where the SOAP/Axis Servlet just acted to interpret and translate the payload into a normal urlencoded or multipart form-data post to the Struts Interface. Michael Oliver AppsAsPeers LLC 7391 S. Bullrider Ave. Tucson, AZ 85747 Phone:(520)574-1150 Fax:(520)844-1036 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>