[esb-issues] [JBoss JIRA] (JBESB-3874) Improve RemoteWsdlLoader error messages and logging

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/JBESB-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730987#comment-12730987 ] 

RH Bugzilla Integration commented on JBESB-3874:
------------------------------------------------

tcunning at redhat.com changed the Status of [bug 819852|https://bugzilla.redhat.com/show_bug.cgi?id=819852] from NEW to MODIFIED
                
> Improve RemoteWsdlLoader error messages and logging
> ---------------------------------------------------
>
>                 Key: JBESB-3874
>                 URL: https://issues.jboss.org/browse/JBESB-3874
>             Project: JBoss ESB
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Web Services
>    Affects Versions: 4.11
>            Reporter: Tom Cunningham
>             Fix For: 4.11 CP2
>
>
> 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"

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira