sorted by: recent | see : popular

Content Tagged with SCA + choreography

Choose the right XML parser for your implementation. You have a choice of using either a DOM-based, SAX-based or a StaX-based XML parser.

The Abstract WSDL documents business-specific information. The Concrete WSDL however is technical in nature and may have nothing to do with business-specific information.

Repeated calls over the network can degrade the performance of your system. For read intensive type services that provide relatively static content like historic data or catalog information, cache as much data as you can ...

Repeated calls over the network can degrade the performance of your system. For read intensive type services that provide relatively static content like historic data or catalog information, cache as much data as you can ...

If multiple short messages are being exchanged between the client and the service, setting up security either through SSL over HTTPS or WS-Security may not be optimal because of the handshake overhead involved in setting it up.

WSDL-based Web Services define a stateless model and an unordered set of operations. WSDL and therefore WSDL-based web services do not have the concept of state ...

WSDL-based Web Services define a stateless model and an unordered set of operations. WSDL and therefore WSDL-based web services do not have the concept of state ...

Do not rely on the SOAP action header for message routing purposes. The HTTP binding SOAP action field is not available in the SOAP 1.2 specification and has already been deprecated in the WS-I basic profile specification too.

Depending on the nesting levels of the parameter types, XML and SOAP message overhead can grow significantly.

At times an XML could contain characters or declarations that are not supported by SOAP or the runtime - examples are, DTD declarations, binary data, locale specific character encoding, etc. In such cases you may have to use Base64 encoding of the raw byt

At times an XML could contain characters or declarations that are not supported by SOAP or the runtime - examples are, DTD declarations, binary data, locale specific character encoding, etc. In such cases you may have to use Base64 encoding of the raw byt

You have to stay away from the tendency to use an xsd:string element to represent your whole message body.

In the same service either expose all your operations with document/literal or as rpc/literal. Do not mix the style/use alternatives in the same Service.

When exposing a service interface to external clients, always expose Request/Response Message Exchange Patterns (MEPs) as much as possible since they work best with HTTP transports and provide interoperability.