Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 24517 invoked by uid 500); 20 Sep 2002 15:59:54 -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 24508 invoked from network); 20 Sep 2002 15:59:54 -0000 Importance: Normal Sensitivity: Subject: Re: cvs commit: xml-axis/java/src/org/apache/axis/i18n MessagesConstants.java RB.java ExtendMessages.java ProjectResourceBundle.java Messages.java To: axis-dev@xml.apache.org X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000 Message-ID: From: Doug Davis Date: Fri, 20 Sep 2002 11:59:52 -0400 X-MIMETrack: Serialize by Router on D03NM119/03/M/IBM(Build V60_09122002|September 12, 2002) at 09/20/2002 09:59:55 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I don't mean this as a comment on this commit (or on Rich of course) but I'm very curious...the async support was -1'd because people didn't want such any new APIs so late in the 1.0 cycle and yet we're allowing redesigns of the build/test structure, the message structure... (any others....?). These types of changes could potentially have a far larger negative impact than introducing *new* APIs. If the new APIs don't work then there's no harm done to the existing Axis users. So I'm curious - why can't the async stuff go in? -Dug rsitze@apache.org on 09/20/2002 11:19:25 AM Please respond to axis-dev@xml.apache.org To: xml-axis-cvs@apache.org cc: Subject: cvs commit: xml-axis/java/src/org/apache/axis/i18n MessagesConstants.java RB.java ExtendMessages.java ProjectResourceBundle.java Messages.java rsitze 2002/09/20 08:19:25 Modified: java/src/org/apache/axis/utils Messages.java Added: java/src/org/apache/axis/i18n MessagesConstants.java RB.java ExtendMessages.java ProjectResourceBundle.java Messages.java Removed: java/src/org/apache/axis/utils RB.java Log: Initial drop of hierarchical messaging. I'm still testing new features, but it passes regression. To extend the messages to a new package - introduce a new message file (currently axisNLS.properties) to that package (or a parent package) - Copy o.a.a.i18n.Messages (all static methods) to the package containing the new message file - Replace any occurances of ''import o.a.a.utils.Messages' with 'import yourPackage.Messages' in all java files in 'myPackage' and all subpackages. - You may put sub-messages files and copies of Messages in subpackages to further extend Messages will look up the hierarchy (but not beyond org.apache.axis) for messages if they cannot be found by the referenced Messages class. - yourPackage.Messages will, as a last effort, link back to o.a.a.utils.axisNLS