Bug 780044 (SOA-2407)

Summary: Web Services that uses WSDL with import statement cannot be proxied with internal:// referred wsdl
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Jiri Pechanec <jpechane>
Component: JBossESBAssignee: Kevin Conner <kevin.conner>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.1.0.ER2Keywords: Regression
Target Milestone: ---   
Target Release: 5.1.0 GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-2407
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-17 09:45:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
wspb.zip none

Description Jiri Pechanec 2010-10-12 09:11:15 UTC
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

Comment 1 Jiri Pechanec 2010-10-12 09:12:13 UTC
Attachment: Added: wspb.zip


Comment 2 Kevin Conner 2010-10-12 10:14:54 UTC
The issue appears to be related to the way in which WebServiceUtils (in ESB) searches for the wsdl, will get this addressed.

Comment 3 Kevin Conner 2010-10-12 10:36:57 UTC
Link: Added: This issue depends JBESB-3503


Comment 4 Kevin Conner 2010-10-18 08:32:02 UTC
Link: Added: This issue is duplicated by SOA-2434


Comment 5 Laura Bailey 2010-12-17 00:41:25 UTC
Writer: Added: Darrin


Comment 6 Laura Bailey 2010-12-17 00:47:59 UTC
Release Notes Docs Status: Added: Not Yet Documented


Comment 8 Jiri Pechanec 2011-01-11 11:55:17 UTC
Verified in ER6

Comment 9 Dana Mison 2011-02-17 09:45:08 UTC
Release Notes Docs Status: Removed: Not Yet Documented Added: Not Required