[ https://issues.jboss.org/browse/DROOLS-424?page=com.atlassian.jira.plugin... ] Damon Horrell commented on DROOLS-424: -------------------------------------- The configuration part of this would be easy. e.g. in the xsd: <xsd:attribute name="type" use="required" type="knowledgeSessionTypeEnum"/> could be replaced with: <xsd:attribute name="type" use="optional" type="knowledgeSessionTypeEnum"/> <xsd:attribute name="scope" use="optional" type="knowledgeSessionScopeEnum"/> <xsd:simpleType name="knowledgeSessionScopeEnum"> <xsd:restriction base="xsd:string"> <xsd:enumeration value="request" /> <xsd:enumeration value="session" /> <xsd:enumeration value="application" /> </xsd:restriction> </xsd:simpleType> and then in KnowledgeSessionDefinitionParser, scope="request" would be equivalent to type="stateless", and scope="application" would be equivalent to type="stateful". The new option would be scope="session". However I'm not sure when the StatefulKnowledgeSession would actually be created as it requires access to the HTTP session to store it for future requests. Does the HTTP request get passed all the way through from Camel to the Drools classes? I tried tracing it through but lost it somewhere in the depths of Camel. -- 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