Pinned topic Cast Iron & RESTful services
Can anybody give some information about how to use RESTful services in Cast Iron?
RESTful Services2011-01-12T14:26:59ZThis is the accepted answer. This is the accepted answer.
REST services are most commonly implemented as (serialized) XML over HTTP. To provide a REST service, an orchestration begins with an HTTP Receive Request and probably use a Transform Read XML to convert the HTTP body (string) to an XML document. To invoke a REST service, populate the XML document and serialize it using Transform Write XML. The output string is used to populate the body of an HTTP request that is sent using the HTTP Post Request activitiy.
Re: RESTful Services2013-01-25T06:51:35ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
Can we not implement/invoke the Rest web services using the Provide Service and Invoke Service activities provided by Cast Iron?
Re: RESTful Services2013-01-25T13:55:04ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
REST is a bit "simpler" since it only requires HTTP. There is no direct equivalent to a WSDL for RESTful services (I am not sure what is happening with WADL). The HTTP methods (POST, GET, PUT, and DELETE) may be involved in supporting a set of CRUD activities. An advantage of release WebSphere Cast Iron release 6.3 is that you can establish HTTP method based listeners instead of using a single listener and then conditionally choosing a path of execution.
With RESTful services, the structure of the payload that may accompany a POST or PUT must still be mutually agreed upon by the service provider and consumer. JSON is often used for representing structured data but any mutually agreed upon message type may be used.
Also, WSDL-exposed services may also use invoke using just HTTP. For example, a "Transform Write XML" and "HTTP Post Request" (or Invoke Request from 6.3) can be used in place of a "Web Services Invoke Service". Similarly, a "Web Service Provide Service" is roughly equivalent to a "HTTP Receive Request" followed by a "Transform Read XML".
A problem with traditional WSDL based web services is that an external SOAP layer is responsible for parsing and serializing the exchanged XML document. If an inbound document cannot be parsed, the sending client gets an HTTP 500 error and the document is never seen by the receiving service.
SwethaRai 270005X65V48 Posts
YPS1_guybrush_guybrush 060000YPS147 Posts
Re: RESTful Services2013-10-16T12:18:41ZThis is the accepted answer. This is the accepted answer.
- SwethaRai 270005X65V
Have a look on the articles here, i'm suppose it contained enough reference to start with REST based implementation.