I would not want to argue about workitemhandlers. Since my priority is to get
my code base 5.1.0 RELEASE ready. They work for me, as I said, using a
simple Spring <util:map>. This approach is used by many developers, and I
don't need anything else here. Thank you.
As far as creating and reloading the Session [ that is where I need more
understanding ], kstore seems to be pretty involved to use as client APIs:
kbase,
configuration and
environment
as oppose to: knowledgeProvider.newStatefulKnowledgeSession( [ nothing
here ] ); [ the way it used to be ]...
As to Spring creating a Session.. I understand this part [ will need to
scope it prototype ].
What I still do not fully understand, [and I did not have time to solve the
new source code puzzle yet] is when I need to reload the session having just
a sessionID, how can I do it without using "KnowledgeStoreService"?
[ Since right now I have a very simple implementation that creates a new
Session by newStatefulKnowledgeSession(), and when Activity is completed, it
reloads an existing one by just the sessionID ]
--
View this message in context:
http://drools-java-rules-engine.46999.n3.nabble.com/5-1-0-CR1-Drools-Spri...
Sent from the Drools - User mailing list archive at
Nabble.com.