snip... > another thing we should start looking at which is distributed domain > support. Hopefully the endpoint changes that went into M2 will help > and I'd like to start looking at that and what we can do to support > proper dynamic operation with nodes coming and going, don't expect > that would get finished for M3 but some start at least would be good.
+1 I think we should bring the domain back in now and am happy to help if needed. > > Not directly related to 2.x i think we should look at trying to use > Hudson for the nightly builds. it would be worth tying to see if it's more friendly than confluence. > > ...ant > I need to do a bit more work to get rid of the old EndpointReference structure. I want to copy over some 1.x changes as a prelude to bringing up binding.jms. We may even be able to make a start on getting that in I'd like to get stuck into making the OASIS tests run and fixing and conformance changes they identify. We don't have to wait for tests of course if we know where changes are required for OASIS. Also need to add the fix to allow the write operation to determine what version of the SCA is in place to the correct processors can be chosen. We need to decide if the builders are going to be backward compatible. This probably comes under the domain heading as, IIRC, our baseline solution is to treat a node as supporting SCA 1.1 or 1.0. It's the domain that would have to deal with both flavours. Simon
