I'm quite interested in the concept of software components and how those ideas can be applied to Java code. Thoughts or ideas I have on this subject get dropped here for the benefit of humanity and my own hubris.
Except where otherwise noted, all original content is licensed under a
Creative Commons License.
See details.
Looks like I’ll be speaking at the Portland Java User’s Group this evening (October 28th). My discussion will be on how to better structure you applications with components and CBD. The first half of my talk will be on general concepts and tips for making better components, and then I’m going to use the JavaBean architecture as a basis for describing how to make these components.
Tomorrow after the show, I’ll put up the slides. If you are interested in hearing a discussion about component-based development in Java with Java Beans, come on over.
© 2003-2005, Howard Abrams • Except where otherwise noted, all original content is licensed under a Creative Commons License (see details).
As promised, you can look at my presentation or download the PowerPoint version (and if you missed the show, there are lots of copious notes to gander at).
How did it go? While I wasn’t in the audience, I think the presentation went fairly well. I really enjoyed myself and hope it was useful to those nearly comatose observers.
I did realize that there is a significant problem conceptualizing “reusable components.” I don’t blame anyone, as it does take a shift in thinking. After the show, I was talking to a number of people, and they would present their project, and it would be clear that all the work they were putting into their program would never be used again.
One guy was explaining how a series of forms would dump data into a series of JavaBeans, and then on command would write themselves into a database (well, that’s a simplified version of his idea). I asked him why spend any effort on those JavaBeans since he will never use such application-specific JavaBeans again.
Instead, I could see creating a JavaBean that could store parameters into a hash (granted even that sounds like controller glue-code), and build another bean that given a hash would store it into a database (although those sorts of database components are already written).
In fact, I’ve got a couple of components that I could present the servlet parameters and have it store those values in a database … and I could do the entire thing in a bean connector IDE like AppComposer without writing any new code.
Granted, I believe I am over-simplifying his application, but I do think that we often tend to overly complicate our applications, and I’m really convinced that CBD (and her new baby sister, SOA) can make applications (and your programming life) much simpler.
Comment posted on Wednesday, 29 October 2003
|
|
|
|
|
|