Page History

...

Validation rules are taken from the binding schema and the OSOA and OASIS specs:

• http://www.oasis-open.org/committees/documents.php?wg_abbrev=sca-bindings^{Image Removed} (sca-binding-jms-1.1-spec-cd01-rev4.pdf)
• http://www.osoa.org/display/Main/Service+Component+Architecture+Specifications^{Image Removed} (SCA JMS Binding V1.00 )

...

The JMS binding is aware of the following policy implementations.

• org.apache.tuscany.sca.binding.jms.policy.header.JMSHeaderPolicy
  • Used to set various JMS message headers including JMSType, JMSCorrelationID, JMSDeliveryMode, JMSTimeToLive, JMSPriority and arbitrary user defined header properties
• org.apache.tuscany.sca.binding.jms.policy.authentication.token.JMSTokenAuthenticationPolicy
  • Used to insert a user defined authentication property into the JMS header.

Intents and policy sets can be constructed to control the application of these policies. The following intents are defined by default

• pritority
• deliveryMode

New intents and policy sets can be designed are required to provide the level of control you need over your application.

...

the "operationSelector" and "wireFormat" elements are declared in the tuscany namespace (http://tuscany.apache.org/xmlns/sca/1.0^{Image Removed}). The default operation selection and wire format behvaviour is defined in the JMS Binding Specification 1.0 but we have added a selection of other formats and selectors as alternatives.

...