axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Doug Davis <>
Subject Re: cvs commit: xml-axis/java/src/org/apache/axis/i18n
Date Fri, 20 Sep 2002 15:59:52 GMT

I don't mean this as a comment on this commit (or on Rich of course) but
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....?).
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
to the existing Axis users.  So I'm curious - why can't the async stuff go
-Dug on 09/20/2002 11:19:25 AM

Please respond to

Subject:    cvs commit: xml-axis/java/src/org/apache/axis/i18n

rsitze      2002/09/20 08:19:25

  Modified:    java/src/org/apache/axis/utils
  Added:       java/src/org/apache/axis/i18n
  Removed:     java/src/org/apache/axis/utils
  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 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
    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

View raw message