Use a Java Proxy instead of a JCA Adapter

[thorsten_nordholmsbirk]

h5. Introduction    Occasionally, one comes across an intgration scenario for which XI's standard adapters do not suffice. Creating a new JCA adapter is always an option, but it is often overkill for dealing with relatively simple communication requirements. Furthermore, an adapter module is usually inappropriate for handling actual communications. This blog illustrates an approach which uses a Java Proxy to handle the communications instead.   I won't explain proxy development per se in this blog, since it has been described at some length in other blogs and in the XI documentation:   ** [Using Acknowledgments with XI 3.0 Java Proxies | https://weblogs.sdn.sap.com/pub/wlg/3531 [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken]] **   ** [An Illustration of Java Server Proxy | An Illustration of Java Server Proxy] **   ** [Asynchronous Inbound Java Proxy | Asynchronous Inbound Java Proxy.] **   ** [SAP Library | http://help.sap.com/saphelp_nw04/helpdata/en/44/79973cc73af456e10000000a114084/frameset.htm] **     h5. Example    As an example case, consider the HTTP adapter. One thing it is (unfortunately) incapable of doing is transfering dynamic message content to the URL query string.   Say, for example, we are requesting a list of search hits from Google  (http://www.google.com). The search string can be submitted as part of the URL query string, e.g. http://www.google.com/search?q=XI  (http://www.google.com/search?q=XI) (which searches for "XI"). Now let's say the search string is part of the request message: