Wade, et al, Jeremy seemed to do a good job of compiling a structured way ahead. I could be wrong, but I recall no significant response to his idea. I recommend rallying around Jeremy and implementing his idea.
Sam On Thu, Nov 20, 2008 at 3:55 PM, Wade Chandler < [EMAIL PROTECTED]> wrote: > Where are we? I am very interested in contributing more towards that 3.0 > release or what ever...where it really becomes River and things start anew > in a sense. I have some NetBeans things I *must* attend to in the near term, > but certainly would love to help with tooling for NB and some other things. > What needs to happen for the next release for those bugs which are fixed or > being fixed to be released as essentially the last bits of incubator > releases and working towards the main goals of this past conversation? > Trying to keep the interest moving, but I also have some applications I'll > be using Jini in the near term :-D > > Thanks, > > Wade > > ================== > Wade Chandler, CCE > Software Engineer and Developer, Certified Forensic Computer Examiner, > NetBeans Dream Team Member, and NetBeans Board Member > http://www.certified-computer-examiner.com > http://wiki.netbeans.org/wiki/view/NetBeansDreamTeam > http://www.netbeans.org > > > > ----- Original Message ---- > > From: Calum Shaw-Mackay <[EMAIL PROTECTED]> > > To: [email protected] > > Sent: Friday, November 14, 2008 10:47:43 AM > > Subject: Re: Future of Jini/River > > > > Niclas - > > > > Can you please elaborate on this? I 'd just like to know, I've been > > working with DI concepts using Jini configuration, as well as > > dynamic,event-based reconfiguration through Thor? > > > > Just wondering if this is within the scope that you're thinking of > > > > Cheers > > > > Calum > > > > > > > * Configuration System. Although I like it in principle (after all I > > > was in the JSR-78 EG where it came to light in the first place), BUT > > > it needs better adjustment to agile and TDD methodologies. Perhaps it > > > is only a documentation issue, but I have been faced with using > > > filesystem files to get things going. InputStreams are the way to go. > > -- Sam Chance 443-694-5293 (m) 410-694-0240 x108 (o)
