I am confused with These terms, i am not coming out with examples or accurate results while studying these
Could please share me an example to explain these terms, or how to understand them
Lightweight Objects: I am getting it in AWT language. But how generally it could be explained?
A heavyweight component is one that is associated with its own native screen resource (commonly known as a peer).
A lightweight component is one that "borrows" the screen resource of an ancestor (which means it has no native resource of its own -- so it's "lighter").
Does, in general, this means object of Derived Class is Lightweight Object?
Even when we read following statement:
An entity is a lightweight persistence domain object.
Lightweight means? It borrows something from ancestor which means? it does not have it ows? correct?
Business and Domain Objects
Are these EXACTLY same?
as i read
A business object usually does nothing itself but holds a set of instance variables or properties, also known as attributes, and associations with other business objects, weaving a map of objects representing the business relationships.
Like i am making application which process one record from database, for that it calls web service and put data into database. I Just declared one object which is handling all this, so it would be termed as Business object?
as i also read
business objects and domain objects are collections of properties, modelled after the real-world entities you want to manage with your application
Which means both are same?
Domain should be like object dealing with particular domain type like i take example object having Medical knowledge only have different components of object having Non medical knowledge. So in total both are business objects and each are domain too
Azrael Noor wrote:I am confused with These terms, i am not coming out with examples or accurate results while studying these
I suspect that these terms may have a specific meaning in whatever you're reading.
The only one that I can offer an opinion on is a "Business Object", because I used to be a data modeller.
A Business Object is an object that has some meaning to the "business" - nothing more, nothing less. They often have a close relationship to Business Processes, and will usually be well-defined by the business itself; so you will have little to explain when dealing with non-computer staff.
Examples might include: "Customer", "Invoice", "Month-end", "Cash-out", "Stock", "Stocktake" and gazillions more.
The only other thing I remember about them from when I was modelling was: "Call 'em what the client calls 'em...even if you think it's stupid."
Isn't it funny how there's always time and money enough to do it WRONG?