This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
Support I have a stateless session bean in my class diagram. My controllers are decoupled from the stateless session bean via the use of a business delegate. If the session bean exposes operations/methods: oper_1,...,oper_N - do people think it is overkill to have the same method names in the delegate. Personally, think it makes things look very cluttered
I had a similar issue. But the fact is that a business delegate shields clients from business services, so the methods may or may not have the same name. It may look cluttered / redundant, but it's not wrong. E.g. you may have a method in your BD named fetchUser(Long id), which calls a session bean method named searchUserById(Long). Or it may have the same name. Depends on your naming convention and if you like the adopted approach.
SCJP 1.4, SCWCD 1.4, SCBCD 1.3, SCJD, SCEA/OCMJEA
Live life to an interface, not an implementation!
Joined: Mar 02, 2009
subject: Using a business delegate within the class diagram for assignment