--- In [email protected], "Rob Eamon" <[EMAIL PROTECTED]> wrote: design/solution "might" be use both of these styles. > > Some say that "request customer info" is an event. I understand the > point of view but I believe events are more along the line > of "customer info changed" or "order placed" or "inventory below > threshold" or other such activity. > I view "order part" more in line with the business event, while "customer info changed" is more of a technical event.
Using a simple REA methodology to find events, an contracts between two agents would be more of "keep inventory at xxx" and a business event associated with the contract to fulfill that commitment would be "order yyy parts". "inventory below threshold" to me is more of a notification or information (technical) event based on the stated of the inventory that may be used to invoke a business event. > > That aside, IMHO, after partners negotiate a contract, a > > commitment between the partners is created. The commitment may be > > fulfilled by creating an event between partners, that may invoke > > a service. > > We can put this concept into supply chain using trading partners. :> > > The key word is "may." A service-oriented solution does not > necessarily need to be event-oriented/event-driven nor vice versa. A > particular Agreed on "-oriented" and "-driven". But should SOA consider events or just services. H.Ozawa
