Constructor vs getter,setter

This is a long discussion on that subjetc here:

http://stackoverflow.com/questions/1632058/java-constructor-with-large-arguments-or-java-bean-getter-setter-approach

I usually put in the constructor something without which this class will not normall exist
or the object will not make sense.

Something which will have to be changed back and forth during the lifetime of the object
I set in the setter methods.
I still often end up adding getters and setters, which I didn't plan to have
in the very beginning as I then have a need to add more options which I didn't have in mind
in the beginning.

Of course if you write huge projects where you want to think all details over before
actually doing something then you'll probably do it differently.

And more of the general wisdom (vs my habits) on this point here:

http://stackoverflow.com/questions/4943816/field-initialization-in-class-constructors-direct-or-through-setter

Thanks Yan,

One more things is incase of Standalone Java application , if i need to transfer a value from Object Class A to Object of class D , A calls B , B calls C and C calls D ... so in this case the only way it to pass the values through all these classes right ... eventhough its not being used by B and C ??
Or is there a better way of handling these scenerios .