The solution is to fix the component scooped references in
the ibm-webservicesclient-bnd.xmi file. This screen shot shows both a
correct reference and an incorrect reference. The correct reference is to
the ejb-name from the ejb-jar.xml file, which is to the name
ISOProxy. The incorrect reference, the one which causes the
WSWS0052E and WSWS1066W messages is to
ejb/iso/proxy/ISOProxyLocalHome.
This configuration change can be done using either of the
following:
1. Modify the ibm-webservicesclient-bnd.xmi file to correct the
following line to read:
<componentScopedRefs
xmi:id="ComponentScopedRefs_1106920593880"
componentNameLink="ISOProxy">
2. Add the link to the ejb-name using the deployment descriptor editor
in Rational® Application Developer and remove the incorrect link, as
illustrated here:

References:
See this link for a WSClientExtension sample configuration:
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-base-dist&topic=xwbs_sampconfig
For a list of valid ibm-webservicesclient-bnd.xmi tags for WebSphere
Application Server V6.0 Web services, see:
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-base-dist&topic=twbs_configibmclientdd
For a list of valid ibm-webservicesclient-bnd.xmi tags for WebSphere
Application Server V5.1 Web services, see:
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v51x&product=was-base-dist&topic=rwbs_assembpropclient
|