• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

JavaBean convention

 
Joshua Fix
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The interface provided for my assignment only provides methods to return String[] for each record. This pretty much prevents me from following the JavaBean convention and storing each record as a "DatabaseRecord" object. Since there is no provided method to return any sort of collection, it appears that I am forced to submit a series of individual "read" requests for each record in the database.

This seems very odd to me. How will the client know how many records to request? And why on earth would Sun force you to not use the JavaBean convention? I feel like I'm missing something...
 
Soroj Margun
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
It depends on your design. Nothing can prevent you from using OO design concept. The hint is abstraction and layering.
Eventhough the assignment spec. is very strict on some odd things, it also very flexible on many unspecified things. You can design everything on your own way as long as all "must" statement is satisfied
[ June 17, 2008: Message edited by: Soroj Margun ]
 
Jose Luis Iturbide
Ranch Hand
Posts: 73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello.

The interface defines the operations to manage the data storage at low level as part the integration layer.

You can use a bean class but it will be part of another layer.

Regards.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic