Overall thats sounds great. A couple of comments inline. ...ant
On Fri, May 29, 2009 at 1:36 PM, Simon Laws <[email protected]> wrote: > It's always a good idea to try things out. I'd like to help and in > particular I'm interested in what is specific to Tomcat and what > constitutes more general interfaces/patterns for managing > contributions/composites/nodes. I'm looking for the APIs and the > crossover to the more general distributed domain. To aid that I'd like > (us) to bring in the domain manager code in parallel. If nothing else > we can steal bits of code from it. > I'm not totally thrilled about bringing in the old domain manager code right now, i wont get in the way but i don't think its helpful. We can see the code already as its in 1.x and take bits from there if required so i don't see the need to bring it up in 2.x yet. Why i don't like this is because it comes with a large amount of baggage and to get it going would mean taking all that on right away without getting any sort of common understanding or consensus on what we need or are trying to support, and as we've seen over and over it can be real hard to remove or substantially redesign something once its committed. I was hoping this time we'd take small incremental baby steps getting consensus and specific testcases working one by one. > Comments in line > > On Fri, May 29, 2009 at 11:43 AM, ant elder <[email protected]> wrote: >> On Thu, May 28, 2009 at 11:39 AM, Simon Laws <[email protected]> >> wrote: >> >>> I'd like to expand a little on what actual scenarios are being >>> discussed here. >> >> This discussion may well go on and on without achieving much as >> happened in some previous discussions without specific objectives so >> as a concrete scenario as what i'd like to get working is the SCA >> domain used by the new Tuscany Tomcat integration which would work as >> follows: >> >> - The tomcat instance would be a domain. It could also be useful for a >> Tomcat instance to contain multiple domains or be part of a wider >> domain but i'd like to leave those complications to later. > > Sounds ok. > >> >> - SCA contributions (webapps and jars/zips etc) can be added during >> runtime so the domain needs to support adding and starting >> dynamically. Stopping, updating, and removing would be good too but >> that can be left till later > > Right, this is the point about understanding what we mean by dynamic. > There is the perfectly reasonable scenario of incremental deployment > that is enabled by supporting late binding through a registry without > going all the way to dynamic updates. > >> >> - The domain is running within a single JVM so it doesn't need any >> remote distribution technology which helps keep things simple > > I'd like to look at this but it can be done outside of this tomcat exercise. > Sure i agree and i'd planned on in parallel to the tomcat work continuing to also using the two-nodes-itest as a very simple JSE testbed, and we come come up with more simple testcases as the scenarios are developed. ...ant
