Is it acceptable for an interface definition to contain references to other interfaces?

Question

I was looking at the definition of Spring's PlatformTransactionManager which contains references to TransactionStatus and TransactionDefinition, two other interfaces.

Is this acceptable in general, an interface's definition containing references to other interfaces? When is it useful?

Answer 1

Yes it's acceptable. Why wouldn't it be ?

It's even better to have references to Interfaces instead of concrete classes for what it worth.

Answer 2

It's absolutely acceptable. Sometimes types need to refer to other types - and if those types in turn represent potentially complex services, it's useful to be able to abstract out a general type, often in the form of an interface.

Answer 3

Its possible... Thats one of the key aspects in implementing multiple inheritence

Answer 4

Yes. It is possible. I can not think of any scenario where it may create any problems.