> > >It doesn't pretend to do logging, which is what you need for failure >recovery and reliable 2pc. Do you have any evidence that anything else is >ever causing problems in it? Much to my surprise, all the bugs I've >thought were definitely in the tx manager turned out to be in my code;-) >(OK, there were a couple of minor tweaks I made). >
Bugs... in my own code? Ha, you are funny. =P >Tyrex is way way way more than a tx manager-- it includes all sorts of >things such as connection pooling. I don't think relying on it is a >terribly good idea for the long term. I would rather see us add logging to >our tm. Perhaps we can get Ole to give us a little advice on this one. If >we use the jdk 1.4 nio maybe it even won't be ridiculously slow;-) > I was only implying that we don't have to build every component... if there is something out there which is better... lets use it. I don't know about the Tyrex case, which is why I asked for opinions. Grow by aquisition where possible, it will allow us to get there faster.... as long as integration and maintence overheads are kept in check that is. --jason _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
