It seems to me that you should consider refactoring your actions.
I would make a separate class that Action B delegates to in order
to create the JPG data. Then Action A can use this other object
without any problem. If there is shared state between the two, and
you need to have the same instance
At the risk of starting up the old philosophical debate...
You could just instantiate Action_B in Action_A and call execute yourself:
Action actionB = new Action_B();
actionB.execute(m, f, r, r);
I'm not sure exactly what your Action_B is doing, so maybe that won't
work, but it's an option to co
2 matches
Mail list logo