• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Questions about automatic failure

 
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have some questions about automatic failure in the assignment...

1) Have the server have a option to specify the database file location, right?

2) In the client side, one record is booked when the field "customer" has a not blank value. So, a booked record cannot be booked by another client, right?

3) In the client side, one record is booked when the field "customer" has a not blank value. What are you putting in this field?

4) In the client side, one record is booked when the field "customer" has a not blank value. I have to provide a "unbook" method?

5) I think that the "unbook" method is different from the "delete" method. The first could be released and used by several clients, the last makes the record available as "slot" to new records.

6) The assignment do not say nothing about it, I have to provide a implementation of the "create" method in the client GUI? I implemented it in the "Data" class.

Regards,

Luiz Reginaldo
 
Ranch Hand
Posts: 39
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Erm... maybe you can re-read your instruction again? Everything should be stated there.
 
Luiz Reginaldo Curado
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yeah, Shan, I see all this topics there. But I'm afraid of my understanding of those items... I don't want to receive a "automatic failure" message from Sun.
 
Ranch Hand
Posts: 1847
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
what are your thoughts? Just pasting a laundry list of requirements and asking how everyone else has implemented them is not the way things work here.
 
Luiz Reginaldo Curado
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Jereon,

> what are your thoughts? Just pasting a laundry list of requirements and > asking how everyone else has implemented them is not the way things work > here.

I'm don't asking how everyone has implemented, I only wanted to know if my understanding of the problem is correct. What's the problem in doing this? We are sharing ideas, not code!
 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi, I'm brand new here looking for some great idea's and while browsing I saw your questions. Some of them look pretty easy to answer so I just registered myself to do so...

Your question:
1) Have the server have a option to specify the database file location, right?

Answer:
You better should read the instructions on this: I guess you should hold the databasename and hostname and portnumber in a properties file called suncertify.properties. The values must never be edited by hand but always through the gui you create.

Your question:
2) In the client side, one record is booked when the field "customer" has a not blank value. So, a booked record cannot be booked by another client, right?

Answer:
Right!

Your question:
3) In the client side, one record is booked when the field "customer" has a not blank value. What are you putting in this field?

Answer:
The instruction file tells you the answer: you can assume the user to know the clients' ID which must be used to fill the "owner" (that's the name in MY file, maybe it's different from your?) field.

Your question:
4) In the client side, one record is booked when the field "customer" has a not blank value. I have to provide a "unbook" method?

Answer:
Imagine you are the user! Shouldn't you want to be able and correct a wrong chosen room for reservation? Or imagine a client that has booked a room, but decides to cancel it again? I should say: yes, you need to have a way to unbook!

Your question:
5) I think that the "unbook" method is different from the "delete" method. The first could be released and used by several clients, the last makes the record available as "slot" to new records.

Answer:
I agree!

Your question:
6) The assignment do not say nothing about it, I have to provide a implementation of the "create" method in the client GUI? I implemented it in the "Data" class.

Answer:
I guess you should do the implementation just as you did (in the Data class) and simply USE it from your GUI...
 
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by John Hessing:
Your question:
4) In the client side, one record is booked when the field "customer" has a not blank value. I have to provide a "unbook" method?

Answer:
Imagine you are the user! Shouldn't you want to be able and correct a wrong chosen room for reservation? Or imagine a client that has booked a room, but decides to cancel it again? I should say: yes, you need to have a way to unbook!



That would be right if we were talking about a real life application, but this is the SCJD and I don't want to implement more requirements than I need to.
 
Greenhorn
Posts: 28
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'd agree with that, if its not stated in the instructions, its not a requirement. Therefore if implemented, its not a specified feature, just something that you thought would be useful.
 
Ranch Hand
Posts: 117
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
my thoughts on an Unbook method:

what's the difference between providing an "unbook" method, and simply re-booking the record with a blank customer ID?

Answer: Nothing. It's a design decesion. You can do either.

Just remember this: You have been provided an interface (mine was called DBMain). This interface doesn't supply either a book or unbook method. If you decide to provide a facade or proxy of adapter or whatever you want to call it, with a book and unbook pair, you can do that. But it's not necessary.

I didn't see anywhere in my assignment where it dissalowed "Re-booking", espcially at the DBMain level, where it doesn't even understand the concepts of booking and unbooking.

Hopefully, that answers your question.

- Adam
 
Luiz Reginaldo Curado
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for all replys!

I will share my experience with you after submit my assignment.
[ August 23, 2006: Message edited by: Luiz Reginaldo Curado ]
 
John Hessing
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all there,

Maybe it's a little bit late to post a new reply on this, but I've been very busy so I've read all the replies just a moment ago.

About the 'unbook' function again: you all say, what not is asked for, we don't need to deliver, wright?
Wrong!!!

Have a look at the last chapter of the instructions ("What to do if you have a question
"). As you can read there, things are left out on purpose. We need to work with "realistically imperfect specifications", just as in real life. So that's why I think you should not only build exactly what is asked for.
Agree?
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic