Re: BART branch merge

2007-09-04 Thread Maciej Szefler
Sanjiva, Thanks for the pointer, I'll do that. -mbs On 8/31/07, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: > > Hi Maciej, > > > JMS will work with Axis2 as it currently does (that is to say there is a > > possibility of messages being lost). Reliable JMS will require a little > bit > > more

Re: BART branch merge

2007-08-31 Thread Sanjiva Weerawarana
Hi Maciej, JMS will work with Axis2 as it currently does (that is to say there is a possibility of messages being lost). Reliable JMS will require a little bit more cooperation from AXIS. The specific problem is in reliable, we'd need axis to start a TX when a message is received from a partner

Re: BART branch merge

2007-08-31 Thread Tammo van Lessen
+1 from me 2007/8/31, Maciej Szefler <[EMAIL PROTECTED]>: > If you have a custom IL, then there will be some small changes > (for the better), otherwise there's no user-visible differences. > > -mbs > > On 8/31/07, Paul Brown <[EMAIL PROTECTED]> wrote: > > > > +1 to get it merged into trunk and ba

Re: BART branch merge

2007-08-31 Thread Maciej Szefler
JMS will work with Axis2 as it currently does (that is to say there is a possibility of messages being lost). Reliable JMS will require a little bit more cooperation from AXIS. The specific problem is in reliable, we'd need axis to start a TX when a message is received from a partner (i.e. a reques

Re: BART branch merge

2007-08-31 Thread Alex Boisvert
+1. Let's take the trunk (essentially 1.1) and send it into a maintenance branch (based on feedback, we might want to do a 1.1.1) What are the current options for reliable and transacted invocations with the two current ILs? For example, does JMS work with Axis2/JBI? How about transacted? Ar

Re: BART branch merge

2007-08-31 Thread Maciej Szefler
If you have a custom IL, then there will be some small changes (for the better), otherwise there's no user-visible differences. -mbs On 8/31/07, Paul Brown <[EMAIL PROTECTED]> wrote: > > +1 to get it merged into trunk and baked. Sounds like good material > for a 1.2 release. Are there any incom

Re: BART branch merge

2007-08-31 Thread Paul Brown
+1 to get it merged into trunk and baked. Sounds like good material for a 1.2 release. Are there any incompatibilities introduced, i.e., will someone's 1.1 setup work (without modification) in 1.2? -- Paul On 8/31/07, Maciej Szefler <[EMAIL PROTECTED]> wrote: > Hi all, > > With 1.1 all spiced a

BART branch merge

2007-08-31 Thread Maciej Szefler
Hi all, With 1.1 all spiced and cured, I'd like to merge BART branch into the trunk. As a a reminder (its been a while) the BART branch is a refactor of the engine that provides several benefits: 1. Simplified integration -- in particular it is no longer necessary to start transactions in the IL