Jun 16th, 2010, 02:45 PM
Where should the business logic reside. We have been thinking of using BO which wraps the JPA entity and put our business logic into it. BO will be used a prototype bean + a provider (per BO Object) which convert JPA entity into BO + a service per BO.
I think using this approach we are adding lots of layering. Also the BO are not meant to be used by the UI component (in our architecture)
Does the above approach solves the martin fowler suggestion
"At its worst business logic can be very complex. Rules and logic describe many different cases and slants of behavior, and itís this complexity that objects were designed to work with. A Domain Model creates a web of interconnected objects, where each object represents some meaningful individual, whether as large as a corporation or as small as a single line on an order form." - Martin Fowler
or it making our domain model - anemic
Please suggest some alternative ways???
Jul 9th, 2010, 03:49 PM
Can you deliver integrated and reliable information—inside and outside your organization—in a format that all users can understand? And are you able manage that from a single management console that allows you to support your performance management, reporting, and query and analysis end-user requirements?
Introducing BusinessObjects™ XI. With BusinessObjects XI, you can go beyond the limits of traditional business intelligence (BI) suites. By extending the reach of information to all users in your organization, BusinessObjects XI redefines the way your organization captures and shares knowledge. Users get the information they need in a way they understand. And best of all, information is delivered within their current environment, where they work-accurately and securely.
Free Hindi Songs | Wholesale Jewelry
Jul 10th, 2010, 04:41 AM
I am referring to BO in context of java design pattern http://java.sun.com/blueprints/corej...essObject.html