Developing a RESTful Service

Services are used to invoke a process and to call out of the process so that a process receives data from a service and routes data to a service.

The key abstraction of information in REST is a resource. REST ignores the details of component implementation and protocol details. TIBCO BusinessWorks™ Container Edition currently allows the following HTTP methods to be performed on resources: GET, PUT, DELETE, and POST. Both XML and JSON are supported as data serialization formats along with support for definition of custom status codes, path(URL) parameters, key-value parameters, query parameters, and custom HTTP headers.

General Restrictions

  • No wildcards or attribute wildcards. For example, any element and any attribute is not supported.
  • Complex types might not contain both an attribute and a child element with the same local name.
  • Complex types might not be of the pattern "simple type plus attributes".
  • Complex types might not contain mixed content.
  • Attributes that are not part of the default (empty) namespace, cannot be used for Complex Elements.
  • The 'choice' and 'sequence' compositors might not have maxOccurs > 1 (same as the restriction on 'all' in the schema specification).
  • Substitution groups are not supported.
  • Element of simple type with an attribute is not supported.
  • The elementFormDefault can only be qualified for schemas used by REST binding and JSON activities.
  • Schemas should not contain cyclic dependencies within same schema, or on the other schemas.
  • Schemas should not have a type that has two child members with the same local name, but different namespaces.
  • For float and double values, XML schema always shows exponential values of type 1.0E0