Community
Java Today


Most Active Communities
|
| What's
Happening in Java Today |
Fewer Gurus Needed: Look around at the tasks you perform every day. How did you learn them? When you are trying to lend credibility to an approach you took, do you walk through the code and show the advantages or do you quote a guru who recommends taking that approach. Sometimes knowing who recommends an approach is helpful. It provides context for the recommendation. » Read more
(August 12, 2003 6:59AM PT)
 |
 |
Using RSS in JSP pages:
This article aims to show how you can use the Informa API to quickly access RSS feeds to add dynamic news and information content to your web sites. » Read more
(Aug 08, 2003)
|
 |
 |
 |
Multithreaded Tests with JUnit:
JUnit is the glue that holds many open source projects together. But JUnit has problems performing multithreaded unit tests. This article introduces a JUnit extension library designed to enable multithreaded unit testing in JUnit. » Read more
(Aug 06, 2003)
|
 |
Why extends is evil:
Alan Holub argues why you should write most of your code in terms of interfaces instead of extending concrete base classes in Why extends is evil. In his most recent JavaWorld article, Holub begins with an example of the benefits of using superclasses or interfaces when specifying the type of a variable, parameter, or return value from a method. He then sharpens his argument to demonstrate why interfaces are preferred over extending a base class.
» Read more
Designing with Interfaces:
In his article on Designing with Interfaces, Bill Venners writes "Java's interface gives you more polymorphism than you can get with singly inherited families of classes, without the "burden" of multiple inheritance of implementation." His examples demonstrate how the classic diamond problem is avoided with inheriting interface and not implementation and also how to mix composition with interfaces for additional flexibility in your application.
» Read more
 |
What do Customers Mean by "Standards"? (the 6 W's of Standards)
When an ISV tries to sell a new piece of software these days, they are likely to be asked whether the product is based on "standards". I'd like to try to explore what qualifies as a standard in a customer's mind. To do this, I'll try to break down the Who, What, Where, When, Why, and How of standards.
|

|