:-( And DON'T break the build like I just did...
<sigh>
I KNOW I checked that... but that was before this mornings patch to fix
junit.
<ras>
*******************************************
Richard A. Sitze
IBM WebSphere WebServices Development
Richard Sitze/Austin/IBM@IBMUS
09/20/2002 11:06 AM
Please respond to axis-dev
To: [EMAIL PROTECTED]
cc:
Subject: Re: cvs commit:
xml-axis/java/src/org/apache/axis/i18n MessagesConstants.java RB.java
ExtendMessages.java ProjectResourceBundle.java Messages.java
My focus in on the extensability of AXIS, to allow it to be incorporated
into varying projects/environments. So, this is not so much a functional
requirement (new function/feature), but support for extending the messages
within the AXIS framework.
Yes, it does have broad ramifications. It's also clear if it's broken,
there is little question if I get it right/wrong. Finally, as broad as
the changes are, they don't really impact other development much (unless I
screw up)- as I'm playing with the underlying code of this key component
and not the interface.
(Hey, *I* tried to play with the interface, I was voted down also :-)
<ras>
*******************************************
Richard A. Sitze
IBM WebSphere WebServices Development
Doug Davis/Raleigh/IBM@IBMUS
09/20/2002 10:59 AM
Please respond to axis-dev
To: [EMAIL PROTECTED]
cc:
Subject: Re: cvs commit:
xml-axis/java/src/org/apache/axis/i18n MessagesConstants.java RB.java
ExtendMessages.java ProjectResourceBundle.java Messages.java
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
[EMAIL PROTECTED] on 09/20/2002 11:19:25 AM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
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
