Hi Devs, Current GFac runtime context hierarchy is confusing and I think there is a mismatch between what actually happens inside GFac and the current context hierarchy which includes JobContext, InvocationContext, MessageContext, ExecutionContext and SecurityContext.
As I understand what really happens inside GFac Core(only considering job execution; deployment is excluded in this) is as follows(please correct me if I am wrong): * Workflow interpreter or Axis2 Service invoke submitJob operation of * GFac API with required information(input message, security related * information, application description) and when invoked GFac Core * will execute 'in handler chain', actual application(or job) and * finally the 'out handler chain' before sending response message back * to the client. According to above, I think it's enough to have MessageContext(to represent input and output message), JobExecutionContext(represent single execution of a application; will contains both input and output message contexts and ApplicationContext) and ApplicationContext(Application related configuration required to execute application). I am going to implement above in the branch created to refactor GFac. Please feel free to comment on this. Thanks Milinda -- Milinda Pathirage PhD Student Indiana University, Bloomington; E-mail: [email protected] Web: http://mpathirage.com Blog: http://blog.mpathirage.com
