Glenn Vanderburg | Java.net

My pages	Projects	Communities	java.net

Get Involved About java.net Request a Project Publicize your Project Submit Content java-net Project Java.net Enhancements Site Help Report Inappropriate Content Get Informed Articles Blogs Events java.net Online Books java.net Archives Get Connected java.net Forums Wiki Javapedia People Partners Jobs RSS Feeds Java User Groups Search Web and Projects: Online Books: java.net on MarkMail: Advanced Search
		Glenn Vanderburg Glenn Vanderburg is a consultant with Delphi Consultants in Dallas, Texas. An early adopter of Java, he wrote the first advanced Java programming book, published in early 1996. Glenn speaks across the country on a wide variety of software topics, and enjoys helping his customers build powerful and cost-effective solutions. Weblogs Collaboration Software (and a great demo) (After the flurry of blogging last week at JavaOne, I've had to concentrate on work for a while. But I have a lot of notes from the conference that I'll continue to write about for a while.) Heading Out JavaOne is still going on for a few more hours, so a show wrap-up may be premature. But I have to leave early, so it's time to summarize my experience, at least. Macs everywhere ... almost. The first conference I attended after getting my TiBook last year was O'Reilly's Open Source Convention, and I was amazed to see more Macs than any other kind of laptop there. JavaOne is a... Community Seeding, Community Building I've been anticipating this reaction. It was inevitable. But we're not blogging JavaOne because we're... At least the comedy worked ... The "opening act" for this morning's general session was Don McMillan, a self-described "Engineer/Comedian" who started things off with an... Bitter EJB (This is a long blog entry ... you have been warned.) Big conferences like JavaOne are always accompanied by the introduction of new books. This time's no exception. One Big Happy Family I remember being at JavaOne in 1999 (I think) when I first heard the terms "J2SE", "J2EE", and "J2ME". I understood the reasoning for such a move, but at the same time I hoped they wouldn't go...