Sorry about the tone.
+1 to discussing whether to use a Deserializer interface approach or
another approach. I agree that this decision is not 'cast in stone' but it
should be discussed in a forum.
-1 to making code changes to force a coding direction that is known to
affect others.
+1 to Glen removing the code (which he has done). We can discuss the
direction of this code next week.
Cool have a great weekend.
Rich Scheuerle
XML & Web Services Development
512-838-5115 (IBM TL 678-5115)
Sam
Ruby/Raleigh/IBM@ To: [EMAIL PROTECTED]
IBMUS cc:
Subject: RE: cvs commit:
xml-axis/java/test/encoding DataDeser.java DataDe
05/24/2002 09:47 serFactory.java DataSerFactory.java
TestDOM.java TestDeser.java TestHrefs
PM .java TestSer.java
Please respond to
axis-dev
Rich Scheuerle wrote:
>
> Thanks for the heads up, Glen. Oops I guess you didn't give me a heads
up. We need this to be put back in immediately.
>
> Letting me know after the fact is not an appropriate way to make a point.
>
> Please take out your changes and we can discuss this on the Tuesday chat.
Or are conceeding that no else's opinion matters.
Come on, lets play nice now boys and girls.
The proper way to handle this, per http://xml.apache.org/decisions.html, is
as follows:
-1 - "No." On issues where consensus is required, this vote counts as a
veto. All vetos must contain an explanation of why the veto is
appropriate. Vetos with no explanation are void. No veto can be
overruled. If you disagree with the veto, you should lobby the person
who cast the veto. Voters intending to veto an action item should make
their opinions known to the group immediately so that the problem can be
remedied as early as possible.
- Sam Ruby
