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.
Originally posted by Isaias C. Barroso: Hi all, In what situation is more interesting to utilize Home and Remote Objects? Have a pattern for this. Thanks
If requirements dictate a remote business tier, then you'll need a way to communicate across that physical distribution, in which case using a session bean to access the remote business tier makes sense (Session Facade). Remember though that distribution brings with it much complexity, so you certainly don't want to do so just because it's "interesting" ;-) If you have a local business tier, then you can still use EJB, using Local Session beans as a Service Facade, providing transaction semantics and declarative security support. Alternatively, if you have a local biz tier and are not using EJB, then you can use a Plain Old Java Object (POJO) Facade to coordinate access to your business objects. We cover these issues in more detail in our book. Thanks
<i><b>- Dan Malks</b></i><br />Co-Author of <a href="http://www.corej2eepatterns.com" target="_blank" rel="nofollow">Core J2EE Patterns: Best Practices and Design Strategis</a>