Why Mashups = (REST + Traditional SOA') * Web 2.0 : Blog the web All that would change now is the HTTP action parameter. This would basically equate to the database transaction or (CRUD Action - Create, Read, Update or Delete) that is wanted to be performed: RESTful web services have open been mentioned as alternatives to 'Traditional SOA' (SOAP / XML-RPC), however, I believe they need to work hand-in-hand to provide a mix of sources for Mashups (and Mashup editors) . With web services that are generally SOAP-based, the request and response are hidden. SOAP requests must be interpreted as they are received at the server to determine the operation to perform and the arguments required to perform that operation. They are generally passed through as a parameter, which is essentially a function/method call. Why Mashups = (REST + Traditional SOA') * Web 2.0 : Blog the web
Consider-GlassFish-ESB-v2-for-SOA-Tooling Objectives After working through the examples in this article, you should be able to do the following: Install NetBeans IDE and the GlassFish ESBCreate a simple Business Process Execution Language (BPEL) 2.0 projectUse the following BPEL nodes in designing a process: Process Start, Receive, Reply, Invoke, Assign, PartnerLink, Process EndUse the Mapper feature of the Assign nodeCreate a simple Composite Application ProjectCreate a simple Composite Application Service Assembly (CASA)Create a Composite Application Test Case within NetBeans IDEDeploy a Composite Application (JBI and BPEL modules) to GlassFish ESB Background Confession: I am a pragmatist. Consider-GlassFish-ESB-v2-for-SOA-Tooling