project_key: SOA See attached log and example. The @WbService bean contains reference to file with contract definition that contains and import statement referring to an XSD file stored on the disk. The Web Service itself is functioning, WSDL is available from console. But if an jboss-esb.xml file contains definition like <action name="proxy" class="org.jboss.soa.esb.actions.soap.proxy.SOAPProxy"> <property name="wsdl" value="internal://jboss.ws:context=Quickstart_webservice_proxy_basic_ws,endpoint=HelloWorldImportWS"/> </action> then the deployment fails with an exception Caused by: org.jboss.soa.esb.ConfigurationException: java.lang.NullPointerException at org.jboss.soa.esb.actions.soap.proxy.SOAPProxy.<init>(SOAPProxy.java:193) ... 90 more Caused by: java.lang.NullPointerException at java.net.URI$Parser.parse(URI.java:3003) at java.net.URI.<init>(URI.java:578) at java.net.URI.create(URI.java:840) at org.jboss.soa.esb.actions.soap.proxy.SOAPProxyWsdlLoader.load(SOAPProxyWsdlLoader.java:155) at org.jboss.soa.esb.actions.soap.proxy.SOAPProxy.<init>(SOAPProxy.java:188) ... 90 more This scenario worked in 5.0
Attachment: Added: wspb.zip
The issue appears to be related to the way in which WebServiceUtils (in ESB) searches for the wsdl, will get this addressed.
Link: Added: This issue depends JBESB-3503
Link: Added: This issue is duplicated by SOA-2434
Writer: Added: Darrin
Release Notes Docs Status: Added: Not Yet Documented
Verified in ER6
Release Notes Docs Status: Removed: Not Yet Documented Added: Not Required