Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

beta exams and java version for exam

 
Evgeni Shuster
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello. I saw some people did beta exams. For example, SCJP 1.5 beta.
Where can I find information about beta exams.
Also, I passed SCJP 1.4 and now I prepair for SCJD.
What version of Java should I use?
Are both versions (1.4.2 and 1.5) allowed?
If yes, which one preffered?
 
peter wooster
Ranch Hand
Posts: 1033
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Evgeni Shuster:
Hello. I saw some people did beta exams. For example, SCJP 1.5 beta.
Where can I find information about beta exams.
Also, I passed SCJP 1.4 and now I prepair for SCJD.
What version of Java should I use?
Are both versions (1.4.2 and 1.5) allowed?
If yes, which one preffered?


There is no SCJD beta available at present. Both 1.4.2 and 1.5 are allowed when doing this project. I'd recommend sticking to the 1.4 features as you are likely to find much more information both in print and on this forum. There has been some discussion about the use of the new 1.5 concurrent programming classes, but not much else.
 
Liang Anmian
Ranch Hand
Posts: 119
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As long as the version you are using is not superceded by another version for more than 1.5 years, you are fine. So in this case, 1.4 and 1.5 are acceptable.

I'm now using 1.5 for this project. Beware though, depending on the way you have chosen to implement this project, you may be forced to forsake RMI. This is what happened to me. The reason is due to my decision to use the new ReentrantLock class to implement locking. However, the lock and unlock methods of that class must be called by the exact same thread, else an exception will be thrown. For RMI, I cannot control which thread on the server will service the client, so lock and unlock will most likely be called by different threads. Due to this, I'm forced to use Sockets.

I'm still going to use 1.5, although I have to use Sockets. For some reasons, now I feel that Socket is easier for my design, as now I have complete control of how the server works. By using RMI, almost everything is controlled by the RMI mechanism. I actually find that RMI is not as flexible. If you design your architecture well, it is not impossible to create an easily maintainable socket solution.

For the new concurrent package, I find that only the lock classes (e.g. ReentrantLock) are useful for the assignment, regardless of which one you got. The rest are over the head.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic