I use JavaBeans still.  They are an alternative to using PHP or old
school ASP.  I agree that EJB/J2EE is the REAL Web Java though.

I personally prefer Java as a language and thats the reason that I use
it in development.  I think it offers a lot of benefits over PHP and
ASP.

We use it for our site (www.e-connected.com) and even built our own
eCommerce system in JavaBeans (www.pluglock.co.uk).  Biggest problem is
finding a good host (especially compared to PHP).  www.lunarpages.com
is a good host if you need one.

I did my Final Year Project on J2EE and JavaBeans - if you want a copy
drop me a line (rick.huby AT e-connected.com) - might have some nice
tid bits and leads to get you started (hey I got a high first for that
dissetation so it must be good!)

Hope this helps!

Rick

I guess the question is, how do you define "JavaBeans"? At the
fundamental level, *everything* is "JavaBeans driven in the modern
world -- Hibernate, Struts, JSTL are all driven by that basic bean
motif. I have recently started making sure that all my data beans have
support for PropChangeEvents as well, since I am starting to do a
little more "Fat Client" work now that Java WebStart has taken 90% of
the pain out of that process.

Now, if you are talking about the drag-n-drop gui stuff, no. It hasn't
ever really taken off. At the same time, the .beans package is still
preeminently useful. Especially when combined with the Jakarta beans
and Jakarta collections APIs, it has changed the nature of Java
development into what it is today.

I guess the short answer isn't that "JavaBeans" aren't used, it's that
what "JavaBeans" was about has become so pervasive that it simply *is*
Java now, not something that is an add-on to the established language.