Adding a StatefulKnowledgeSessionAware Interface ------------------------------------------------ Key: JBRULES-2554 URL: https://jira.jboss.org/browse/JBRULES-2554 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-api Affects Versions: 5.1.0.M2 Environment: N/A Reporter: Anatoly Polinsky Assignee: Mark Proctor Priority: Minor Attachments: StatefulKnowledgeSessionAware.java Original Estimate: 1 hour Remaining Estimate: 1 hour Interface to be implemented by any object that wishes to be notified of the {@link org.drools.runtime.StatefulKnowledgeSession} that it runs in. Implementing this interface makes sense for example when an object requires access to session artifacts/details such as rule facts, sessionID, etc. This interface can be implemented by a custom {@link org.drools.process.instance.WorkItemHandler} in case, for example, it needs to access a session to insert / retract some facts before proceeding further to the process node that fires rules ( groups, agendas, etc.. ).

Adding a StatefulKnowledgeSessionAware Interface ------------------------------------------------ Key: JBRULES-2554 URL: https://issues.jboss.org/browse/JBRULES-2554 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-api Affects Versions: 5.1.0.M2 Environment: N/A Reporter: Anatoly Polinsky Assignee: Mark Proctor Priority: Minor Labels: knowledge_session, rulesflow Fix For: 5.3.0.M1 Attachments: StatefulKnowledgeSessionAware.java Original Estimate: 1 hour Remaining Estimate: 1 hour Interface to be implemented by any object that wishes to be notified of the {@link org.drools.runtime.StatefulKnowledgeSession} that it runs in. Implementing this interface makes sense for example when an object requires access to session artifacts/details such as rule facts, sessionID, etc. This interface can be implemented by a custom {@link org.drools.process.instance.WorkItemHandler} in case, for example, it needs to access a session to insert / retract some facts before proceeding further to the process node that fires rules ( groups, agendas, etc.. ).

Adding a StatefulKnowledgeSessionAware Interface ------------------------------------------------ Key: JBRULES-2554 URL: https://issues.jboss.org/browse/JBRULES-2554 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-api Affects Versions: 5.1.0.M2 Environment: N/A Reporter: Anatoly Polinsky Assignee: Mark Proctor Priority: Minor Labels: knowledge_session, rulesflow Fix For: 5.3.0.Final Attachments: StatefulKnowledgeSessionAware.java Original Estimate: 1 hour Remaining Estimate: 1 hour Interface to be implemented by any object that wishes to be notified of the {@link org.drools.runtime.StatefulKnowledgeSession} that it runs in. Implementing this interface makes sense for example when an object requires access to session artifacts/details such as rule facts, sessionID, etc. This interface can be implemented by a custom {@link org.drools.process.instance.WorkItemHandler} in case, for example, it needs to access a session to insert / retract some facts before proceeding further to the process node that fires rules ( groups, agendas, etc.. ).

Adding a StatefulKnowledgeSessionAware Interface ------------------------------------------------ Key: JBRULES-2554 URL: https://issues.jboss.org/browse/JBRULES-2554 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-api Affects Versions: 5.1.0.M2 Environment: N/A Reporter: Anatoly Polinsky Assignee: Mark Proctor Priority: Minor Labels: knowledge_session, rulesflow Fix For: 5.4.0.Beta2 Attachments: StatefulKnowledgeSessionAware.java Original Estimate: 1 hour Remaining Estimate: 1 hour Interface to be implemented by any object that wishes to be notified of the {@link org.drools.runtime.StatefulKnowledgeSession} that it runs in. Implementing this interface makes sense for example when an object requires access to session artifacts/details such as rule facts, sessionID, etc. This interface can be implemented by a custom {@link org.drools.process.instance.WorkItemHandler} in case, for example, it needs to access a session to insert / retract some facts before proceeding further to the process node that fires rules ( groups, agendas, etc.. ).

Adding a StatefulKnowledgeSessionAware Interface ------------------------------------------------ Key: JBRULES-2554 URL: https://issues.jboss.org/browse/JBRULES-2554 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-api Affects Versions: 5.1.0.M2 Environment: N/A Reporter: Anatoly Polinsky Assignee: Mark Proctor Priority: Minor Labels: knowledge_session, rulesflow Fix For: 5.4.0.Final Attachments: StatefulKnowledgeSessionAware.java Original Estimate: 1 hour Remaining Estimate: 1 hour Interface to be implemented by any object that wishes to be notified of the {@link org.drools.runtime.StatefulKnowledgeSession} that it runs in. Implementing this interface makes sense for example when an object requires access to session artifacts/details such as rule facts, sessionID, etc. This interface can be implemented by a custom {@link org.drools.process.instance.WorkItemHandler} in case, for example, it needs to access a session to insert / retract some facts before proceeding further to the process node that fires rules ( groups, agendas, etc.. ).

Adding a StatefulKnowledgeSessionAware Interface ------------------------------------------------ Key: JBRULES-2554 URL: https://issues.jboss.org/browse/JBRULES-2554 Project: Drools Issue Type: Feature Request Security Level: Public(Everyone can see) Components: drools-api Affects Versions: 5.1.0.M2 Environment: N/A Reporter: Anatoly Polinsky Assignee: Mark Proctor Priority: Minor Labels: knowledge_session, rulesflow Fix For: 5.5.0.CR1 Attachments: StatefulKnowledgeSessionAware.java Original Estimate: 1 hour Remaining Estimate: 1 hour Interface to be implemented by any object that wishes to be notified of the {@link org.drools.runtime.StatefulKnowledgeSession} that it runs in. Implementing this interface makes sense for example when an object requires access to session artifacts/details such as rule facts, sessionID, etc. This interface can be implemented by a custom {@link org.drools.process.instance.WorkItemHandler} in case, for example, it needs to access a session to insert / retract some facts before proceeding further to the process node that fires rules ( groups, agendas, etc.. ).