On Fri, Jun 12, 2009 at 10:56 AM, Simon Laws<[email protected]> wrote: > On Fri, Jun 12, 2009 at 10:49 AM, ant elder<[email protected]> wrote: >> On Wed, Jun 3, 2009 at 9:54 AM, ant elder<[email protected]> wrote: >> >>> Smashing. How about aiming for taking an M3 release branch about the >>> 12th, so Friday after next, which should let us get an M3 out the >>> following week. >>> >> >> How is everyone going with M3 work, is it ready to take the branch >> now? Or tomorrow? Or need a few more days? >> >> (Once the branch is taken we'll still be able to merge new changes >> from trunk to the branch for a couple more days till its close to >> making RC1) >> >> ...ant >> > > It depends how much we want to have working. Hoping to bring up dome > more tests today to reinstate callbacks over web services. Also > working through removing the now redundant code. Haven't done endpoint > reference serialization yet so passing callable reference over the > wire won't work (we haven't put those tests in 2.x yet) and on this > point I think we should move up to the OASIS APSI which changes the > nature of ServiceReference and removed CallableReference. > > Remind me what part of the endpoint story you need working for the > webapp work you're doing? > > Simon >
Whats there now is enough to get the simple scenario working of a webapp with an implementation.web component talking to an implementation.java component in a separate contribution (so two nodes, one for the webapp and another for the other contribution). I guess there's no need to hurry though, so would it be worth waiting on M3 slightly to get callbacks going? ...ant
