• 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

JDBC - Design justifications

 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
In part 2, did you justify all design decissions?
I have chosen to use JDBC over entity beans, do I have to justify my reasons for that?
Considering ... 1. Performace 2. Team knowledge 3. Entity Beans sucks (maybe I should skip this one). ... anythinge else?

/Magnus
 
Ranch Hand
Posts: 156
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Magnus Wistrom:
In part 2, did you justify all design decissions?
I have chosen to use JDBC over entity beans, do I have to justify my reasons for that?
Considering ... 1. Performace 2. Team knowledge 3. Entity Beans sucks (maybe I should skip this one). ... anythinge else?

/Magnus



Magnus,

Read carefully the project requirements. Your answer is there!
 
Ranch Hand
Posts: 76
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

I have chosen to use JDBC over entity beans, do I have to justify my reasons for that?
Considering ... 1. Performace 2. Team knowledge 3. Entity Beans sucks (maybe I should skip this one). ...



I assume you mean "JDBC over session beans", right? Browse this forum and you will find lots of threads dicussing this issue. Generally spoken, you are probably better off, if you justify all your architectural decisions.

Lars
 
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Magnus,

You can always provide the reasons/assumptions to justify your design decisions. But please make sure that you cross-check those with the given requirements so that there shouldn't be any contradictions.

My suggestion : Use Entity Beans than writing all JDBC code from scratch. For reading operations (if performance is a major concern), you can follow the Fast Lane Reader pattern. For others, its better to use Entity Beans.
[ April 03, 2007: Message edited by: Joseph A Alexander ]
 
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Ricardo Ferreira,

I'd like to talk to you about your RUP certification. I'm brazilian too. I live at Recife. Please, Could you add me in gtalk? (ffsneto@gmail.com)

thanks in advance,
Francisco Neto.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic