Re: [ajug-members]: SOA Service Definition

[Curt Smith <chsmith@speakeasy.net>]

>  system). I thought that there would be a "Foo Service" with multiple 
> messages/operations like "doFoo", "doBar" and "doBaz".
>

What best describes SOA is a similar one to the EJB coarse/fine grained 
discussions.  The SOAP RPC vs Document Literal comparisons are also 
related to the what is SOA.

Not a definition but a refinement of the above thought is:   an SOA 
ideally represents some atomic business operation [give employee pay 
raise, process PO, make accounts payable disbursement, etc coarse 
grained horizontal business operations].   I personally add that the 
transport can be any appropriate technology [JMS, SMTP, HTTP] using SOAP 
envelope and ideally using SOAP document-literal.   Doc literal would 
pass a <purchase-order>...<purchase-order/> document and the response 
would simply be a receipt acknowledged XML document.   The rest of the 
business work flow would asynchronously respond back to the requesting 
customer status of stock, price changes and shipment or exceptions.   
The customer's system would respond with more conversation in the 
context of this long-transaction ID.   etc etc.

BTW, the middleware's SOA blueprints doc is a nice read.

curt

-- 


Curt Smith
csmith@javadepot.com
(h) 404-294-6686
(w) 404-499-5242