When I search for something too many times, I try to remember to post it here. So, to drop the warnings for type safety when you know all is fine, you can do the following:
@SuppressWarnings("unchecked")
List<CustomerBean> customers = (List<CustomerBean>)session.getAttribute(CSRD_CONTACT_LIST);
A recent thread on Linked In lead me to this site showing how many web sites there are: http://news.netcraft.com/archives/web_server_survey.html
I’m on a roll with the LinkedIn rants today 🙂
Someone once said that failure can only occur when time and resources are limiting factors. In the case of software, all of the above are true, though the most consistent cause I see is that the process of doing the following in order:
1) Set a completion date
2) Define the requirements
3) Design the software
4) Develop the software
5) Change the requirements
6) Wonder what went wrong
Agile is a good step in preventing failure from the above process except that even shops that use Agile often face that the end date is set before work begins and that unrealistic expectations are set at the same time.
Another ongoing issue is that management’s reaction to bad news about meeting functionality or a date is to throw more people on the project and demand more frequent meetings which pull the people most capable of solving the issue away from solving the issue. This trains developers to not communicate issues until the last minute, which accelerates this vicious cycle.
As Dennis Miller used to say “But that’s just my opinion. I could be wrong”
I ran across a question on LinkedIn today and gave a long-winded rant-like response that I thought I would post here, too.
Javabeans are hailed as reusabel software components. Is anybody aware of a market for these wigits?
My Answer: Yes, and it has been dominated by IBM and Oracle for the past decade. When the books were written that proposed business models around the technology the expectation was that Swing would win massive acceptance and that Applets would continue to be the key technology of rich web applications. None of this came to pass.
There was also the expectation of an open market of beans, which missed the fact that most developers would rather write their own and only reuse when directed, or until it becomes a habit from being directed to do so. The reuse is still mostly of internally developed beans or those that are part of vendor applications.
And the vendor applications mostly make the beans proprietary, i.e., they only run within their servers.
The exceptions to my cynical gut-reaction is the FOSS community, where many Java Beans and other reusable components can be found.
As Dennis Miller used to say “But that’s just my opinion. I could be wrong”
A guy I used to work with posted this handy article: