This reference is either acquired through a stringified URI string, NameService lookup (similar to DNS), or passed-in as a method parameter during a call. Object references are lightweight objects matching the interface of the real object (remote or local). Method calls on the reference result in subsequent calls to the ORB and blocking on the thread while waiting for a reply, success or failure. The parameters, return data (if any), and exception data are marshaled internally by the ORB according the local language and OS mapping. [edit]
Bruce makes an interesting comment on business rules too: that “routing logic in process gateways” are not “business rules”. That doesn’t really make sense: for sure some gateways will be process-housekeeping decisions of little interest to the business user, but others will surely embed business-critical decisions. On the other hand, it has long been acknowledged that a best practice for BPM is to delegate such business decisions to a managed decision service - hence the explicit new business rule (aka decision) task in BPMN 2.0. And,in the CEP world, for tools like TIBCO BusinessEvents to invoke a decision managed by its Decision Manager tool.
- leave anything related to transport, communication to other layers- use this revised CEP to express and execute event-relevant logic, the purpose of which is to translate the ambient events into relevant business events- have these business events trigger business processes (however lightweight you want to make them)- have these business processes invoke decision services implemented through decision management to decide what they should be doing at every step- have the business processes invoke action services to execute the actions decided by the decision services- all the while generating business events or ambient events- etc.
Most BREs today are deployed as “decision services”, and are used in “stateless” transactions to make “decisions” as a part of a business process. A CEP application is instead processing multiple event streams and sources over time, which requires a “stateful” rule service optimized for long running. This is an important distinction, as a stateful BRE for long-running processes needs to have failover support - the ability to cache its working memory for application restarting or distribution. And of course long-running processes need to be very particular over issues like memory handling - no memory leaks allowed!
M. Aehnelt, H. Schulz, and B. Urban. Advances in Visual Computing: 9th International Symposium, ISVC 2013, Rethymnon, Crete, Greece, Proceedings, Part II, volume 8034 of Lecture Notes in Computer Science, Springer, Berlin, (2013)
S. Lee. Human Interface and the Management of Information: Interacting in Information Environments, Symposium on Human Interface 2007, Held as Part of HCI International 2007, Beijing, China, Proceedings, Part II, volume 4558 of Lecture Notes in Computer Science, Springer, Berlin, (2007)
D. Morand, I. Garcia, and P. Lalanda. Proceedings of the 16th IEEE International Conference on Emerging Technologies and Factory Automation (EFTA 2011), Toulouse, France, page a.1--a.8. (2011)
S. Bhiri, W. Gaaloul, M. Rouached, and M. Hauswirth. Advances in Web Semantics I: Ontologies, Web Services and Applied Semantic Web, volume 4891 of Lecture Notes in Computer Science, Springer, Berlin, (2009)
C. Wu, V. Potdar, and E. Chang. Advances in Web Semantics I: Ontologies, Web Services and Applied Semantic Web, volume 4891 of Lecture Notes in Computer Science, Springer, Berlin, (2009)
K. Sycara, and R. Vacul\'ın. Advances in Web Semantics I: Ontologies, Web Services and Applied Semantic Web, volume 4891 of Lecture Notes in Computer Science, Springer, Berlin, (2009)