Passwords should never be seen in clear text eg. in transfer objects, or in database columns. So we hash them up. Nothing to it.
We implement a event listener list singleton supporting weak references.
Then we can add listeners to an object we wish to observe, and fire events to its observers, without implementing any such support in the observed objects eg. addListener(), removeListener(), fireEvent().
In the Gooey Beans Info prequel, we explicitly declare properties. Now we allow a bean info instance to be bound to a specific bean, in order to support bound properties ie. firing PropertyChangeEvent's.
Having defined style objects in the Hyper Style prequel, we build an "HTML builder" to generate HTML/CSS.
Do you use Google Reader? But why not?! ;)
Ben Galbraith made the following great point in his recent blog entry in praise of intelligent tools such as IDEA.
We use CGLIB to enhance a half-baked Java Bean with no firePropertyChange() invocations in its setters, into a bean that does fire PropertyChangeEvent's from its setters.
This "Jelly Beans" series deals with data entities, as required for the "Gooey Beans" series' demos. Together with "Hyper Beans", i'm calling them the "Foundation Trilogy" :)
And yes, it's a scifi/fantasy trilogy in 42 parts, essentially about writing database applications using Swing.
Here are some problems and possible solutions (today) relating to bean properties.
Getters and Setters
Problem. We don't wanna write lots of getters and setters, or see them.
Solution. We use our IDE to generate them.
Wishlist. Maybe we wanna fold basic getters and setters right out of view en masse.