The Source for Java Technology Collaboration
User: Password:


Today on java.netNovember 24, 2005

Reelin' in the Years: A short holiday note » Read more
 

Projects & Communities

JDK Community
JDK Starter Bugs: Are you interested in contributing to Mustang but not sure where to start? Try picking off a JDK Starter Bug. This new page lists bugs identified by the JDK team as being particularly suitable for outside developers to work on. A getting started page describes the criteria for starter bugs and shows how to claim a bug, collaborate on it, and submit the fix.»Read more
linux.java.net
JamVM: The Linux Java Community page recently noted a short blog about JamVM, a new Java Virtual Machine which focuses on being extremely small, yet supporting the full spec, including finalization, soft/weak/phantom references, JNI, and reflection. The executable is about 135 KB on PowerPC and 100K on Intel, and has also been run on ARM and AMD64.»Read more

Weblogs

Alexander Potochkin Debugging Swing - is it really difficult ?
Every experienced Swing developer knows that Swing components must be accessed from Event Dispatch Thread (EDT) only. Working with JComponents from any other thread may lead to unpredictable results. Funny thing, I took part in interviewing several java programmers who claimed to know Swing well, but at the same time some of them had no idea what EDT is.   Alexander Potochkin

Crash course in writing code
Following the previous entry on bug handling, here is the second chapter on writing code.    Kirill Grouchnikov

Fernando Lozano Great Expectations and a few disappointments with NetBeans 5
I was always suspicious that NetBeans were a second-class citizen inside Sun, but a recent statement from Robert Brewin threw off many of my fears. Yet I think NetBeans is taking some wrong paths in spite of the great new features.    Fernando Lozano

Forums

Re: Inheritance in jaxb2
It is not always necessary to specify all the classes that are mapped in the JAXBContext.newInstance(..) call. JAXB 2.0 will compute a reference closure on the classes specified. (see javadoc for javax.xml.bind.JAXBContext.newInstance(..) for more information). In this case, since a parameterized list is used as the type of the property, I am not certain that this will work. We will look into this further. In the meantime, please try the above and let us know if it works.  

Re: Chapter 5: Rules of the Game
* Economics. This is wrong. The reason that programmers will ditch one language for another is if it solves their pain. The reason I haven't switched to Python or Ruby for instance is that not only do they not solve any pains for me, but they cause new ones. Show me Ruby without warting, and Python without magic underscores, and I may become more interested. When I switched from VB/C++ to Java it was because it alleviated a huge pain. No such massive pain exists in the Java world (except Struts and XP weenies).  

Also in Java Today

JBoss Labs Podcasts
Damon Sicore's recent JBoss Blogs entry Introducing JBoss Labs Podcasts announces "we've introduced Podcasts at JBoss, and they can be found at our community development web site, JBoss Labs. JBoss Podcasts will cover video and audio training for open source software as well as interviews with professional open source developers." A video feed is currently available and will soon be joined by an audio-only feed and an aggregated feed of all JBoss podcasts.

Plugging Memory Leaks with Weak References
While programs in the Java language are theoretically immune from "memory leaks," there are situations in which objects are not garbage collected even though they are no longer part of the program's logical state. In Plugging Memory Leaks with Weak References, Brian Goetz explores a common cause of unintentional object retention and shows how to plug the leak with weak references.

Do you like Java's checked exceptions?
Yes, they enforce a problem-handling contract
No, the syntax is too invasive
No, they're usually not handled correctly anyways
Something else (please comment)
Poll Results | Archive

JavaOne 2006 Call for Papers: There are only a few days to go for the JavaOne 2006 Call for Papers, which closes on November 30. The CFP page offers guidance in what attendees want -- specifically "talks that deepen their practical knowledge" -- speaker selection criteria, and policies that proposals need to adhere to. Potential JavaOne attendees can voice their opinion on what kinds of sessions they'd like to see on the java.net Planning JavaOne 2006 Forum.

Success Stories | Archive

Related Links




 XML java.net RSS