I'm not entirely sure if I understand your question, but it sounds to me that you're using objects as a way to bundle data together in a class, provide getter and setter methods for the data, and then send the object around between classes which does various work on that object or objects.
The most important thing about object-oriented programming is, I think, division of responsibility. Each class should be responsible for a single area, and should provide all functionality that you require from that area. You shouldn't have to ask an object for data that then needs to be processed if the object could already do that for you.
A trivial example: Say you have a
Date class. It holds the necessary information to represent a date, and you can get and modify that information through
setYear methods. So far it's just a wrapper for data - it doesn't actually do anything, it's not responsible for anything more than holding that data.
So say you want to add a day to a given date object. What would you need to do? Of course, get the day, increment it, and return it by setting a new day. But if it overflows to a new month then you would need to increment the month, and maybe even the year if the month overflows to a new year. But this shouldn't be your responsibility to handle this - this should be part of the
Date class, which should provide you an
addDay method and take care of incrementing the date accordingly.
Take it a step further, and say you wish to find out if a date is a leap year or not. You can do that by checking the year yourself. But that shouldn't be your responsiblity - the
Date class should do that for you through a
isLeapYear method or something. Or say that you want to check if two dates are the same. You can do this yourself by getting and checking the day, month and year yourself, but this should also be the responsiblity of the
Date class - it should provide you with a
Let us further say that you have an
Order class, which contains various stuff that any order should, including a
Date of when it was issued. Say you want to check if two orders were issued on the same date; you can get the date from both orders and check it yourself through
order1.getDate().isEqual(order2.getDate()). But this sounds like something the
Order class should be responsible of - it should have an
areDatesEqual(Order) method and do the work for you.
On the other hand, if you had an
Order object and a
User object and both happen to have a date that you want to compare, then in this case you should do that yourself; the
Order class is only responsible about orders, and the
User class about users. Thus there can be no
areDatesEqual(User) in the
Order class and no
areDatesEqual(Order) in the
User class - that would be a violation of responsibility.