[jboss-jira] [JBoss JIRA] (DROOLS-424) drools-camel support for session-scoped knowledge session

[Damon Horrell (JIRA)]

     [ https://issues.jboss.org/browse/DROOLS-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Damon Horrell updated DROOLS-424:
---------------------------------

    Description: 
The Spring configuration for drools-camel allows creation of either a stateless knowledge session (i.e. effectively request-scoped), or a single stateful knowledge session which is shared by all requests (i.e. effectively application-scoped).   There is no session-scoped option.

This differs from the earlier drools-execution-server module (version 0.0.4) which was replaced by drools-camel.  drools-execution-server maintained a separate StatefulKnowledgeSession instance per HTTP session.

Can you please add support for a session-scoped StatefulKnowledgeSession?

  was:
The Spring configuration for drools-camel allows creation of either a stateless knowledge session (i.e. effectively request-scoped), or a single stateful knowledge session which is shared by all requests (i.e. effectively application-scoped).   There is no session-scoped option.

This differs from the earlier drools-execution-server module which was replaced by drools-camel.  drools-execution-server maintained a separate StatefulKnowledgeSession instance per HTTP session.

Can you please add support for a session-scoped StatefulKnowledgeSession?


    
> drools-camel support for session-scoped knowledge session
> ---------------------------------------------------------
>
>                 Key: DROOLS-424
>                 URL: https://issues.jboss.org/browse/DROOLS-424
>             Project: Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.6.0.Final
>            Reporter: Damon Horrell
>            Assignee: Mark Proctor
>
> The Spring configuration for drools-camel allows creation of either a stateless knowledge session (i.e. effectively request-scoped), or a single stateful knowledge session which is shared by all requests (i.e. effectively application-scoped).   There is no session-scoped option.
> This differs from the earlier drools-execution-server module (version 0.0.4) which was replaced by drools-camel.  drools-execution-server maintained a separate StatefulKnowledgeSession instance per HTTP session.
> Can you please add support for a session-scoped StatefulKnowledgeSession?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira