Hi, Thanks for starting this up.
For the policy related work, I am presently looking at JAAS and trying to bring that into Java Impl container to enable us to get a better idea of how to design PolicyHandlers in general. This must be in before next week. I am not sure if I'd be able to get support for reliability into the ws-axis2 binding before next week. If you are going to cut a branch by end of next week then I'd prefer that subsequent updates are first done onto the branch and then merged into the trunk. I suppose this is what the others also mean when saying that they'd like to continue work on the trunk. - Venkat On Dec 12, 2007 4:29 AM, Simon Laws <[EMAIL PROTECTED]> wrote: > Hi > > Following on from the JIRA tidy up note here are a few high level areas > that > I've seen activity on over the last few weeks and so may be ready to go > for > release 1.1. > > Deep tomcat integration > Better JMS support > JAXB based POJO transformations. > More policy function > Modeling of client side java script components > JSONRPC reference binding > Better support for doman API suggested by assembly spec > Domain based and standalone node operation > Domain lookup for remote access to domain services. > Transactions > JPA > Class loading and OSGI > BPEL fixes > Distribution structure changes > > Can you fill in the detail and tell me what we can get in, i.e.add what is > missing from the list, add details to what is on the list, indicate what > shouldn't be on the list. Think of this as forming the CHANGES text so it > should look like [1]. Even better go and update the CHANGES doc:-) > > As a reminder here is the timeline I'm working to. I'm planning on > spending > next week working on the first RC. Building the distribution, fixing > samples, READMES, licenses etc. The objective being to have a release > candidate before I go away for the holidays for people to review at their > leisure. This means that when everyone is back we can spend the week > beginning 7th Jan knocking it into shape until we get an RC we can vote > on. > The following week, beginning 14th would also be taken up by voting with a > view to releasing the week beginning 21st (or earlier if we get done). > > Does that still sound reasonable to everyone. Are there pieces of function > that must be in 1.1. that can't be done in this timescale? > > Regards > > Simon > > [1] > > http://svn.apache.org/repos/asf/incubator/tuscany/java/sca/distribution/src/main/release/CHANGES >
