Dave Siracusa [
http://community.jboss.org/people/davesiracusa] replied to the discussion
"WSDL11Reader.java has problems w/ included WSDL"
To view the discussion, visit:
http://community.jboss.org/message/548900#548900
--------------------------------------------------------------
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
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
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/548900#548900]
Start a new discussion in JBoss ESB Development at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]