Community

I created a workaround:

I created a custom action which constructs a SOAPProxy via reflection (guest-class).

Prior to SOAPProxy construction I load (guest_wsdl) the wsdl and transform it (guest-xsl).

I stored the corrected wsdl to the file system, so SOAPProxy can pick it up (wsdl).

<action name="proxy"
        class="com.company.soa.esb.bus.bpesb.actions.WrapSoapProxyAction">
               <property name="guest-class" value="org.jboss.soa.esb.actions.soap.proxy.SOAPProxy" />
               <property name="guest-wsdl" value="http://devkopbpbs01.yb.int/metaverse/soap?wsdl" />
               <property name="guest-xsl" value="/transforms/Fixup_Metaverse_Types_WsdlTransform.xsl" />
               <property name="wsdl" value="file://../deploy/metaverse.wsdl">  
                      <http-client-property name="max-total-connections" value="100" />
                      <http-client-property name="max-connections-per-host" value="50" />
               </property>
</action>

I also created a contract publisher, in order to handle relative file path (wsdl).

@Publish(BPSOAPProxyWsdlContractPublisher.class)
public class WrapSoapProxyAction extends ActionProxy  {
...

Please let me know whether a JIRA gets created for this issue.

Best,

Dave