This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
In other words a framework for Collections, Lists, Sets, etc. that notify interested parties of mutations? I have a need for some data models that are for all intents and purposes just Collections that need to be observed. Looking at Jakarta there's some work on the subject but it's not released and Google isn't turning up anything. Am I stuck rolling my own API and decorators here?
Nope. I'm interested in mutations in the Collection not mutations in the elements, what I want to do is far easier. I'm well on my way to finishing a reasonably simple API now, I was hoping to avoid the hassle and find something more robust but it doesn't look like there's anything out there.
Yeah, that's the unreleased work at Jakarta I mentioned. The API there is getting awfully big too. I understand why but personally it feels like trying to be too robust at the expense of an easy to use, light API.
I've implemented what I needed to in two interfaces and two classes. I'll keep an eye on your GlazedLists and what Jakarta is working on, I certainly think your API looks attractive if I needed to model tabular data. However, this particular case seems just "too simple" and using it would be massive overkill at the expense of readability and understanding.