2.1 changes - how to proceed

[Wouter Cloetens <wc...@raleigh.ibm.com>]

I've gotten very far this weekend. The changes are massive. I've
touched over half the source files...

I'm a bit reluctant to commit this stuff before it's properly tested.
Especially, I'm not familiar with XMI, use of the envelope filter (I
propose that as a new name for "transport hook extension" as it doesn't
really work at the transport layer since the introduction of MIME
functionality), the fault listener functionality, any of the scripting
stuff and the SMTP transport. I don't have the setup to test EJBs
anymore.

Would you guys propose that I commit the changes, risk breaking some
functionality or introducing bugs in the latest CVS, but fix those as
people test and report problems, or should I make my in-progress tree
available elsewhere and wait until it's stable to commit?

bfn, Wouter
--
http://www.workspot.net/~zombie/soap/
My opinions are irrelevant. They will be assimilated by my employer.

Re: 2.1 changes - how to proceed

[George I Matkovits <ma...@uswest.net>]

Darn. (-: I was under the impression that you committed your changes on
Saturday night.) I got the CVS tree, added your 'better' fix and run
Yaron's  3 parallel * 10000 tests = 30000 test cycles OK. At least we know
that your 'connection' fix works perfectly :-) Could we get a parallel CVS
tree built somewhere?
Regards - George

Wouter Cloetens wrote:

> I've gotten very far this weekend. The changes are massive. I've
> touched over half the source files...
>
> I'm a bit reluctant to commit this stuff before it's properly tested.
> Especially, I'm not familiar with XMI, use of the envelope filter (I
> propose that as a new name for "transport hook extension" as it doesn't
> really work at the transport layer since the introduction of MIME
> functionality), the fault listener functionality, any of the scripting
> stuff and the SMTP transport. I don't have the setup to test EJBs
> anymore.
>
> Would you guys propose that I commit the changes, risk breaking some
> functionality or introducing bugs in the latest CVS, but fix those as
> people test and report problems, or should I make my in-progress tree
> available elsewhere and wait until it's stable to commit?
>
> bfn, Wouter
> --
> http://www.workspot.net/~zombie/soap/
> My opinions are irrelevant. They will be assimilated by my employer.