Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 24815 invoked by uid 500); 6 Dec 2002 20:23:32 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 24806 invoked from network); 6 Dec 2002 20:23:31 -0000 Message-ID: From: Tom Jordahl To: "'axis-dev@xml.apache.org'" Subject: RE: Planned Post 1.1 Release Changes for the IME stuff Date: Fri, 6 Dec 2002 15:23:37 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N James, +1 to this plan. 1.2 with full backward compatibility. Good stuff! :-) -- Tom Jordahl Macromedia Server Development -----Original Message----- From: James M Snell [mailto:jasnell@us.ibm.com] Sent: Friday, December 06, 2002 2:57 PM To: axis-dev@xml.apache.org Subject: Planned Post 1.1 Release Changes for the IME stuff Ok, I've just been looking at the changes that are going to be necessary (AFTER THE 1.1 RELEASE) to deliver the first phase of the async IME integration into the main Axis code base. Now that the interfaces themselves are mostly stablized and the base implementation mostly complete, the next phase is to start migrating the Transports over to the new model. This change will involve change all Transport Senders into MessageExchangeProviders rather than Handlers. The following files will need to be changed. org.apache.axis.server.AxisServer org.apache.axis.configuration.FileProvider org.apache.axis.configuration.NullProvider org.apache.axis.configuration.SimpleProvider org.apache.axis.deployment.wsdd.WSDDDeployment org.apache.axis.deployment.wsdd.WSDDDeployableItem org.apache.axis.deployment.wsdd.WSDDTransport org.apache.axis.EngineConfiguration org.apache.axis.AxisEngine org.apache.axis.client.AxisClient There may be some other files that are affected, but these are the biggies. The goals of this phase in the transition are: 1. Maintain complete backwards compatibility with all existing Transport implementations and deployment descriptors 2. Maintain complete backwards compatibility with all applications currently using Axis (changes will not propograte up to the client API level) These changes are targeted for the Axis 1.2 release. No changes will be made to these files with regards to this project until after the 1.1 release goes gold. Key todo's other than the code changes: 1. Test cases for the base implementation (in progress) 2. Documentation (in progress) - James Snell IBM Emerging Technologies jasnell@us.ibm.com (559) 587-1233 (office) (700) 544-9035 (t/l) Programming Web Services With SOAP O'Reilly & Associates, ISBN 0596000952 Have I not commanded you? Be strong and courageous. Do not be terrified, do not be discouraged, for the Lord your God will be with you whereever you go. - Joshua 1:9