Home/ Questions/Q 7976837
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-04T09:01:04+00:00

What is the correct way to resolve: Class A { methodDoSomeOperation() { ClassB b.someOperation(…..);

  • 0

What is the correct way to resolve:

Class A {

methodDoSomeOperation() {

  ClassB b.someOperation(.....);
....

 }


ClassB {

someOperation(....) {


 if (this.someCondition) then{
   ClassC c.anotherOperation(....)
  } else {
 ClassD d....
 }
}

 }

Methods c.anotherOperation takes a long time. I would like receive notification regarding what was selected: c.anotherOperation(....) or d..... for display in a user interface before invoking c.anotherOperation.

Something like:

someOperation(....) {


if (this.someCondition) then{
 //notify ClassA what was selected and continue
 ClassC c.anotherOperation(....)
 } else {
 ClassD d....
 }
}

Obviously it is possible to invoke some method in ClassA but this creates strong coupling and confusing logic. Is it possible use some features of Spring?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Would you consider some form of the Observer pattern?
    Whatever the class that is closer to the UI(May be class A?) can be registered as an observer to the Class B. this can be done upfront or as part of the call to the B.SomeOperation() by adding a parameter. Then when you do the check B.someCondition, you can call the registered observer an then call the long running operation on C.

    • 0