Creating literal and encoded web services
With the previous two recipes, Creating a document transport web service and Creating a RPC transport web service, we addressed the transport style aspect of web service definition. This recipe will further address the usage of the SOAP binding. With the transport style, we get four combinations of possible usage as shown in the following table:
|
Transport style |
Use |
|---|---|
|
Document |
Literal |
|
Document |
Encoded |
|
RPC |
Literal |
|
RPC |
Encoded |
This recipe will give an explanation of all four combinations.
Getting ready…
In this recipe, we will amend the example from the previous recipe.
How to do it…
Open the BookLibraryImpl.java class in JDeveloper. Depending on the transport style and use, we modify the @SOAPBinding annotation in one of the following ways:
Document transport style with literal use attribute:
@SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL)
Document transport style with encoded use attribute:
@SOAPBinding(style = SOAPBinding...
