Good suggestions Ant and to get this stuff done we need to make a list and have people pick things off it they want to work on. Otherwise we'll each have a separate list in mind and come February we'll all be frustrated that only 10% of each of our lists is done and we'll be convinced that we're not ready to release.
Trying to pick out a theme here I would subscribe to an approach where we try and get a core set of functions working well rather than throwing everything back in from 1.x straight away and suffer inconsistencies. So I can extend the list further.... Assembly spec compliance Policy spec compliance JCAA spec compliance JCI spec compliance binding.ws spec compliance binding.jms spec compliance (impl bpel spec compliance as a stretch) distributed domain domains in different runtime environments non-SCA client support dynamic rewiring policy support transactions security Consistency of support across all extensions async callbacks interface.wsdl Any more for the list from others? With a list we can prioritize. Experience tells us that we may not get through the whole list before other things come up so we might as well do the things that we consider most important first. Simon
