Popular @
Forum Controls
Spotlight Features
The Rich Engineering Heritage Behind Dependency Injection
Andrew McVeigh takes us on a tour of the rich heritage behind dependency injection, what it represents, and tells us why its here to stay.
NetBeans 6: Matisse Updates
NetBeans 6 delivers great updates to the Matisse GUI builder. Spend a few minutes with Roman Strobl and get an expert briefing on what's new and what has changed. (sponsored)
Introduction to Groovy Part 3
In this, the third and final installation of Andres' Introduction to Groovy series, you learn about how Groovy handles variable numbers of arguments, named parameters, currying, and more about Groovy operators. Including, some new operators.
Easier Custom Components with Swing Fuse
Swing Fuse (actually just Fuse), is a framework designed to make it easier to create your own custom desktop components. In this article, Daniel Spiewak shows you how to get started and provides sample source code you can download.
Benchmark Analysis: Guice vs Spring
Willam Louth shows how he uses JXInsight Probes to investigate probable performance issues with code bases that he is not familiar with. He also highlights possible pitfalls in creating a benchmark, as well as in the analysis of results.
Java SE Intermed Splitting -> Proposal
At 11:00 AM on Apr 13, 2006, Nicolas Brasseur wrote:
Fresh Jobs for Developers Post a job opportunity
After some discussion with John we think that it needs to be split.
In this wiki page I propose the splitting of the Java SE Intermed in several exams.
Java SE Intermed Core Exam
Java SE Common APIs Exam
Java SE Intermed I/O Exam
Java SE (Advanced) Collection Exam (the one from Serkan)
Java 5 New Language Features Exam
Java SE Reflection API Exam
Java SE Tools Exam
What do you think ? Any suggestion is welcome ...
Nicolas
4 replies so far (
Post your own)
Re: Java SE Intermed Splitting -> Proposal
Hi Nicolas, I like this split.May be should we specify that only the "Java SE Core - Intermed" will be mandatory for the orange belt. And we should move it to the green belt ? What people think ?
The sum of these exams is more difficult and goes deeper than the original Java SE Intermed, which is fine.
We could be more generous on the knowlege points. A tiny 5 questions exam may provide 1 knwoeledge point. But I'd give more for a 15 questions exam. So I'd rather give 2 to 3 points (instead of 1 to 2 points) per exam.
For I/O, is there another reason than nIO for the "Intermed" label ? If not, I'd suggest that we have just an IO exam and maybe later a nIO exam for the non blocking IOs, which may be considered as a separate API.
For the exams titles, what about:
- Common APIs -> Base APIs ?
- 5 New Language Features -> Tiger ?
- Reflection API -> Reflection
- Tools -> ??? (I've no good idea but "tools" might be misleading).
Re: Java SE Intermed Splitting -> Proposal
John,regarding I/O, sockets were explicitely excluded from the intermed exam.
What I suggest is that we build 3 exams :
- Java SE (Intermed) I/O : as definded in my previous thread (and we drop Intermed)
- Java SE NIO : as you proposed
- Java SE Networking : Socket, ServerSocket, URL, URI, ... (these topics are not covered yet)
Nicolas
Re: Java SE Intermed Splitting -> Proposal
I think this a great idea! My only concern is what will happen with those who have taken and passed the Java SE - Intermed Exam. Perhaps they might lose the knowledge points but also recieve their contribution points back?I also agree with John, Tools is a bit vauge. Should we break "Tools" down further to a few small exams (5-10 q's, 1 knowledge point).
I very much hope that we can successfully split this exam.
- Eric
Re: Java SE Intermed Splitting -> Proposal
'Tools' is the official name- http://java.sun.com/j2se/1.4.2/docs/tooldocs/tools.html
if you have any other suggestion ...
Concerning points nothing should change, we are creating new exams and 'closing' the old one.
Nicolas