David Jencks wrote: > Hi Igor, > > I'd like to stick with the jboss tm and add the needed functionality. > > Can you outline what you have been thinking of? I want to allow resource manager specific variation of XAResource state change sequence. This way we'll decouple different RMs from each other and developers will be able to concentrate on one RM without concerns to break others. I have very brief idea how this can be implemented, but I believe it is doable and not too complicated.
> Also, is the new xa wrapper in cvs HEAD working well enough to move to 3.2? > Should we even move it to 3.0? What do you think about cached javax.jdbc.XAConnection.getConnection() problem I've mentioned few days ago? Can we afford saying "Oracle 8i is not supported in XA mode"? > I think there may still be issues in what xa flags we send in the start/end > calls, but I haven't had time to make a complete analysis. > > Thanks! > > david jencks > > On 2002.09.27 11:05:57 -0400 Igor Fedorenko wrote: > >>Thank you, David. >> >>JBossTX still has problems with oracle (see for example #614116 I've >>been working on recently) and I was thinking if it worth fixing or we >>can switch to Tyrex. I have a solution that will solve JBossTX >>compatibility problems once and forever, however this solution is not >>trivial to implement and I am looking for alternatives. >> >>David Jencks wrote: >> >>>jboss tm -- fast. Does not handle distributed (multiple jboss >> >>instances) >> >>>tx. Does not do tx logging, so automated recovery is not really >> >>possible. >> >>>tyrex tm -- does handle distributed tx and logging. >>> >>>both will handle xa transactions with many participants where there is >> >>only >> >>>one tm instance and nothing crashes. >>> >>>If you need distributed tx (several cooperating tm) or automatic >> >>recovery >> >>>use tyrex. >>> >>>The "distributed" part is nearly done in jboss 4 for the jboss tm: as >> >>part >> >>>of the jca 1.5 support there is a tx import facility. We just need an >>>invoker that has an XAResource in the client half and uses the Work >>>interfaces in the server half. >>> >>>AFAIK no one is working on the logging part, but I don't see why it >> >>should >> >>>be hard. >>> >>>With logging in place I would expect automatic recovery to be fairly >> >>simple >> >>>also but I haven't thought about it much. >>> >>>david jencks >>> >>> >>>On 2002.09.27 09:37:50 -0400 Igor Fedorenko wrote: >>> >>> >>>>Hi, >>>> >>>>Could somebody give brief comparison JBossTX and Tyrex transaction >>>>manager and explain when I should prefer one over another? Thanks in >>>>advance. >>> >>-- >>Igor Fedorenko >>Think smart. Think automated. Think Dynamics. >>www.thinkdynamics.com >> >> >> >>------------------------------------------------------- >>This sf.net email is sponsored by:ThinkGeek >>Welcome to geek heaven. >>http://thinkgeek.com/sf >>_______________________________________________ >>Jboss-development mailing list >>[EMAIL PROTECTED] >>https://lists.sourceforge.net/lists/listinfo/jboss-development >> >> > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development -- Igor Fedorenko Think smart. Think automated. Think Dynamics. www.thinkdynamics.com ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
