Bug 819852

Summary: Improving SOAPProxy classpath protocol logging messages
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Vinicius <vmartine>
Component: JBossESBAssignee: tcunning
Status: MODIFIED --- QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.3.0 GACC: rwagner, soa-p-jira, tcunning
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 852806 (view as bug list) Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 852806, 860046    

Description Vinicius 2012-05-08 11:48:55 UTC
Description of problem:

Some users are requesting an upgrade on logging/error messages for org.jboss.soa.esb.actions.soap.proxy.SOAPProxy class when using "classpath://" protocol for the following situations:

- I attached a test case for you to try. Just deploy the esb and it should throw "java.net.MalformedURLException: unknown protocol: classpath" Although I 

    -- The NPE is raised on this call:

      org.jboss.soa.esb.actions.soap.RemoteWsdlLoader

	~line 78
  
	else if(url.startsWith("classpath://")) {
        	originalStream = ClassUtil.getResource(url.substring(12, url.length()), getClass()).openStream();
        } 

  - NullPointerException when wsdl is not found in the classpath should have a friendlier message;

  - classpath invalid characters (eg. backslash "\") validation. 

    -- Current message: org.jboss.soa.esb.ConfigurationException: 'url' property is not a valid URI." Test case: change

How reproducible:
Easy

Steps to Reproduce:
1. Deploy the attached  project "UlkoisetYhteydet-EP-esb.esb"

Comment 1 JBoss JIRA Server 2012-11-20 19:30:38 UTC
Tom Cunningham <tcunning> updated the status of jira JBESB-3874 to Resolved

Comment 2 JBoss JIRA Server 2012-11-20 19:30:44 UTC
Tom Cunningham <tcunning> updated the status of jira JBESB-3874 to Closed