Recently I had a chance to look in to BeanContextAPI. It deals with lifecycle of a component. Most of us were not realize that the component has a complex lifecycle. The BeanContext API has a concept of a Service Provider and that Services can be added and removed dynamically with appropriate notification sent to the JavaBean. In essence it covers the concept of dynamic services as opposed to static ones.
In computer science we continue to reinvent things. What i feel is Our inherent weakness is to dismiss old inventions, and therefore throwing out the good design with the bad design. There are just too many cases of good ideas that have been thrown out simply because they are old and not new. The most classic example is the Relational model. We often try to look for another option and then we may come back the classic databases.
Unless untill there is a strong reason to go for new technologies, do not go for it. We should think twice before we go.
So as a word of wisdom. It's always wise to investigate old designs. You leverage the amount of time spent thinking about the subject (yes, they could think back then) and you approach their work from a new perspective. So, if we look at the BeanContext and the JavaBeans API's we realize that there's a lot of useful things in here. It's just up to us to evolve it into the new ways of thinking.
No comments:
Post a Comment