Deploying Web services with Java bindings

For Web services deployed with Java bindings (or EJB bindings even where the Web service is on a different server) you must make additional classes available to the gateway.

Why and when to perform this task

For EJB bindings, make the EJB client JAR file available. If the Web service is deployed on the same server as the gateway, the necessary interfaces and classes are already visible. If not, implement one of the following options:

For Java bindings, make the Java classes for the Web service available by implementing one of the following options:


Related concepts
Data type representation - Choosing between Generic classes and Deployed Java classes
Complex data types - Mapping namespaces to packages
Related tasks
Deploying Web services to the Web services gateway
Related reference
Web services gateway - Supported types



Searchable topic ID:   twsg_admin_bindings
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/twsg_admin_bindings.html

Library | Support | Terms of Use | Feedback