If a SOA composite application uses a web service binding to define an endpoint reference, the composite cannot be invoked from a JSP/Java class. Web services binding is defined with the binding.ws port="" location="" tag in the composite.xml file. The following example provides details:

<service name="client_ep" ui:wsdlLocation="BPEL.wsdl"> 
    <interface.wsdl interface="http://xmlns.oracle.com/Application/Project/ 
      BPEL#wsdl.interface(BPEL)"/> 
    <binding.ws port="http://xmlns.oracle.com/App/BPELProj/ 
      BPELProcess#wsdl.endpoint(bpel_client_ep/BPELProcess_pt)"/> 
  </service> 

Instead, use ADF binding for SOA composite interaction with ADF-BC Web Application. After deployment of a composite with ADF binding, invocation from a JSP/Java class is successful. The following example provides details:

<reference name="ADFWebService"
             ui:wsdlLocation="ADFWebService.wsdl">
    <interface.wsdl interface="http://example.com/hr/#wsdl.interface(HRAppService)"/>
    <binding.adf serviceName="{http://example.com/hr/}HRAppService"
                 registryName="hrapp_JBOServiceRegistry"/>
  </reference>

For this example, hrapp is the ADF-BC web application name.