<p>I listen to the podcast java posse,  on this there is often discussion about components (note components are not (clearly) objects).  They lament the fact that Java does not have components, and contrast with .NET that does.  Components apparently makes developing applications (not just GUI apps) easier.</p>

<p>I can figure from the discussion certain qualities that a component has,  its something to-do with decoupling (substituting one component for another is just a matter of plumbing).  It has something to-do with properties, it definitely has something to-do with events and delegates.   </p>

<p>So to the questions:</p>

<p>./ can anyone explain to me what a component is. (and why java beans are not components).</p>

<p>./ can anyone explain how they help development.</p>

<p>./ can anyone explain why java does not have them if they are so useful.</p>

Software Engineering Radio has an episode on exactly this topic:
http://se-radio.net/podcast/2008-02/episode-87-software-components
The general idea is that a software component can describe what its own dependencies and services are, in the form of metadata. I don't know why you might have heard that Java does not have components, since you can certainly imagine an architecture in Java where components do describe themselves through metadata. I suppose it's just that the Java platform definition by itself doesn't really have a component architecture.
Update: Indeed, one need not imagine such an architecture because as others pointed out, Java Beans or Servlets could certainly be considered component-based architectures.