Using <br> X(...) from entry-point "y" <br>may be used for selecting a subset of events. Given that in STREAM mode events coming from a single entry-point must be ordered by timestamp but that it's not necessary to uphold this restriction across different entry points, I have come up with a use case or two where I have an n:1-relationship between event types and one entry-point, i.e., all events of a type are inserted via one entry point, and this results in the question:<br>
<br>Would it be possible to implement the definition of the default entry point for an Event or Fact type via a metadata attribute, e.g.:<br> declare X<br> @role( event )<br> @entry-point( y )<br> end<br>so that this<br>
a) declares the entry-point in the KnowledgeBase (the same way from entry-point "x" does)<br> b) removes the need to use from entry-point with all patterns referring to X<br> c) would still let me override the entry point with a "from entry-point" clause. <br>
<br>If not discouraged, I'll open a JIRA for an enhancement.<br><br>Wolfgang<br><br>BTW: Java Zone Trailer, <a href="http://www.youtube.com/watch?v=8Px-GHPxB4I" target="_blank">http://www.youtube.com/watch?v=8Px-GHPxB4I</a> (NSFW ;-)<br>
<br>