File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Programmer Certification (SCJP/OCPJP) and the fly likes Confused about tight coupling Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Certification » Programmer Certification (SCJP/OCPJP)
Bookmark "Confused about tight coupling" Watch "Confused about tight coupling" New topic

Confused about tight coupling

Sagar Shroff
Ranch Hand

Joined: Jun 07, 2011
Posts: 209

my question is if for eg there is a class A and class B then if class A uses public methods in class B then class A should be tightly coupled to class i right please help???

Stephan van Hulst

Joined: Sep 20, 2010
Posts: 4624

Yes, in this case classes will be tightly coupled. This is a bad thing.


Wait sorry, I thought you said variables, not methods. When A calls methods of B, it will big coupled to B, but not nearly as tight as it would be if it accessed a public variable of B. The latter case is very very bad.

The mind is a strange and wonderful thing. I'm not sure that it will ever be able to figure itself out, everything else, maybe. From the atom to the universe, everything, except itself.
Sagar Shroff
Ranch Hand

Joined: Jun 07, 2011
Posts: 209

I am Sorry for using those short syntax......

So Stephan does that mean only if a class accesses variable of another class then it is tightly coupled to another class and it is also bad encapsulation. AM i right ??......

And in K.S book it had written that " Tight Coupling is the undesirable state of having classes that has many references to each other ,not well encapsulated..i understood this much but this last statement which says

and the breadth of API usage is more ....So what does this statement means ??
I agree. Here's the link:
subject: Confused about tight coupling
It's not a secret anymore!