Java Reference
In-Depth Information
▪ Using optimization methods, such as FastInfoset and MTOM/XOP
▪ Using headers
▪ Using attachments
▪ If using SOAP, to dictate acceptable style, use, and parameter style values, such as docu-
ment/literal wrapped
▪ Using one-way methods
▪ Using asynchronous clients
▪ Encoding for binary data
▪ Centralized schema
These guidelines should ideally include examples of correct and incorrect use of each item.
There are many more items to consider depending on your implementation choices, system
maturity level, and environment. While the focus of this topic is on Java, you might need to
determine standards relating to service creation in RPG, .NET, or what have you. This list
indicates the appropriate scope of guidelines for your service implementations and SOA. Fail-
ure to adhere to such guidelines can cause interoperability problems and severe performance
degradation, and can waste development time.
NOTE
Keep your standards up-to-date. Make sure to include your team members in determining guidelines.
Receive their feedback openly and incorporate their suggestions as appropriate. Create new items,
drop old or obvious ones, and make updates as necessary to ensure that the guidelines are fresh, rel-
evant, and useful.
Specifications
There are dozens of specifications that can come into play very quickly in the world of SOA
and Java-based web services. Linking to the specifications can help ensure that everyone can
quickly find the definitive answer to a question, and it helps implicitly direct people to what
they must understand to be productive within the SOA environment. Relevant Java specifica-
tions might include the following:
▪ JAX-WS
▪ JAXB
▪ SAAJ
Search WWH ::




Custom Search