• 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

The most important requirement: "It must be J2EE"!?

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi everybody!

I am new to this forum and I am really impressed with the quality of information that I can find here.
Could you share your opinion on the following point?
My assignment says that the most important requirement is: "It must be J2EE".
I have read posts from people that cleared part 2/3 saying that the classes in the class diagram should be technology independent and the J2EE related details could be put only in the component diagram. I can not figure out how this can be done. Could someone explain this?
Does it mean that the class diagram may not present any reference to Session, entity or message driven EJBs and still be J2EE?

I understand that I should protect my design as much as possible from technology dependent details, so I can port it to other platforms. But, in the context of this certification, I think that, at certain point, I will have to come to decisions of how to expose functionality from one tier to another, and this will make me onsider the J2EE options, and these options will influence my design. For example: I will probably implement the customer as an entity EJB and, in order to save network roud-trips while accessing its properties, I will create a value object for it and a business facade as a Session EJB that will receive requests from remote clients and perform the corresponding property handling.
Do you think it is correct? If yes, do you think that I should not express this decisions in my class diagram?

Thank you in advance for your help,
Marcos
[ March 14, 2005: Message edited by: Marcos Mota ]
 
Ranch Hand
Posts: 52
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Marcos,

Yes, IMHO, the class diagram should be technology independent,
component diagram is where I show my J2EE technology related design.

Please take a look at my post which has this discussed in details :
https://coderanch.com/t/153187/java-Architect-SCEA/certification/Passed-SCEA-Part-score


HTH
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic