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

Further Details on SCJD Objectives, Please?

 
Jim Stoll
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm pondering the SCJD exam - I've read Sun's info and have cruised through the list messages here, but am trying to get a solid idea of what's involved so that I can work on my weak areas (of which low-level items such as RMI and Sockets are two... I develop in Java daily, but using higher-level APIs like JDBC, EJB, Swing, JSP, etc and 3rd party tools...)
From what I can gather, we're looking at a client-server style application w/ a fat-client GUI via a custom-built protocol (based on RMI or Sockets, depending on the luck of the draw) that talks to an existing 'database' product that must be modified to resolve concurrency and indexing issues. I'm presuming that no 3rd party APIs are permitted, the 'database is not accessible via JDBC, I can't whip out a copy of Oracle, etc?
How much, if any, of the network protocol exists vs must be built? How about the database? Is the GUI built from scratch or is it an extension of existing code?
Not looking for any exam answers here - just trying to get a solid idea of the scope of the problem so that I can evaluate what its likely to require of me.
Thanks for any help,
Jim Stoll
 
vladimir levin
Ranch Hand
Posts: 45
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
>From what I can gather, we're looking at a client-server style
>application w/ a fat-client GUI via a custom-built protocol
>(based on RMI or Sockets, depending on the luck of the draw)
>that talks to an existing 'database' product that must be
>modified to resolve concurrency and indexing issues. I'm
>presuming that no 3rd party APIs are permitted, the 'database
>is not accessible via JDBC, I can't whip out a copy of Oracle,
>etc?
Yes, I believe this general assessment is correct. It's a *very*
basic app. Your "database" is a single file in a trivially
simple binary format that makes bitmaps look like rocket science.
You have some methods already written that will write to and
read from the "database". You need to write some code to do
a "write lock" at the record level. The only concurrency issue
is the record-level locking so that the user who is "booking
a flight" in the system is guaranteed that the number of seats
available when he starts booking will be there until he's done.
>How much, if any, of the network protocol exists vs must be
>built? How about the database? Is the GUI built from scratch
>or is it an extension of existing code?
The GUI has to be written from scratch. You need to be able to
use a JTable to display flights in the system. None of the
network protocol exists. You can use RMI, in which case you
don't need a protocol, or you can make your own simple protocol
and pass requests and reponses around in the form of serialized
objects. You have a choice which way to go, and will not be
penalized for your choice -- you just need to be able to
justify it in some meaningful way.
I hope this helps...
Vlad
 
Jim Stoll
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for the reply Vlad - sounds approachable! :-) Going to brush up on RMI and sockets for the next week or so and go ahead get the voucher for the programming assignment.
Thanks!!
Jim
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic