I think we should start discussing how this would best be implemented. The big questions is, should we do it in BusinessRulesProcessor, or create a new action? Let me explain....
We could add a configuration option to BusinessRulesProcessor, saying this action instance is only for adding facts into the specified entry-point. This could prove very confusing, however, considering the ability to specify entry-point names within the object-path(s) configuration section is already there. What happens if those two names don't align? ConfigurationException thrown, probably, but why give users the ability to mess up like that?
We could create a new action, perhaps called "EntryPointInserter" (or whatever). Obviously it would need a config option which somehow identifies the stateful session created by BusinessRulesProcessor. For clarity of purpose, it's ONLY job would be to insert facts into ONE entry-point. There would still have to be thread-synchronization done, however. The most annoying one would be because you can already insert into entry-points from BusinessRulesProcessor, what happens if that gets done at the same time this separate action tries to? So, we'd have to be cautious of this.
Thoughts?