The only bigger thing I'm missing in CCs are my "apprising" collections and related utility classes. The main idea behind them is to have the data structure able to serve listeners about internal changes, esp. adds and removals.
public interface ItemMovedSource { public void addItemMovedListener(ItemMovedListener listener); public void removeItemMovedListener(ItemMovedListener listener); }
public interface ApprisingCollection extends ItemMovedSource, ... { }
I also created the exteded versions of "apprisings", called "aware". They are able to report the property changes inside imbedded objects that implements the ProperyChangeSource interface.
public interface PropertyChangeSource
{
public void addPropertyChangeListener(PropertyChangeListener listener);
public void removePropertyChangeListener(PropertyChangeListener listener);
}
public interface AwareCollection extends ApprisingCollection, PropertyChangeSource
{
}
Apprising collection could be easily chained to get more functionality (e.g. filtering, sorting...) without restrictions on mutability of the backed collection - adds/removals are propagated in both directions.
What do you think? Would be such contribution (after several tunings to accomodate Jakarta & CCs conventions and style) to CCs desirable?
Regards David Zejda
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]