the last chapter introduced simple soap messaging. in this chapter, we move to the next level of sophistication and introduce a true messaging framework that forms the backbone of the eai infrastructure developed in this book. this messaging framework enables java applications to send and receive java objects to and from web services using soap as the transport. it also enables asynchronous messaging whereby the sender of a message does not have to block waiting for the receiver to process it. we call our framework the web services messaging framework (wsmf). it is implemented using j2ee and web services standards and serves as the core messaging service used by all the non-jms eai applications developed in the remainder of this book.
the wsmf is not a commercial-quality messaging framework, but rather an illustrative example of how to implement web services oriented messaging within the j2ee environment. in this chapter, you will encounter the major issues associated with implementing soap messaging in java and some solutions that can be applied to your own eai projects.
our wsmf is implemented using the java api for xml-based rpc (jax-rpc). as the reader is probably aware, jax-rpc was created to provide java developers with a standard for incorporating into java applications the xml-based remote procedure call (rpc) functionality described in section 7 of the soap 1.1 specification. jax-rpc was not intended for messaging. the reasons that we have chosen jax-rpc as the standard for our messaging framework are discussed in section 1.1.
in addition to jax-rpc, this chapter introduces two additional standards: jaxb and wsdl. the java architecture for xml binding (jaxb) provides a standard approach, based on xml schema, for serializing and deserializing between xml documents and java objects. the web services description language (wsdl) is a w3c standard interface definition language for specifying web services apis using xml. typically, a web services client reads the wsdl to determine how to structure... 下一页