Bug 819852 - Improving SOAPProxy classpath protocol logging messages
Summary: Improving SOAPProxy classpath protocol logging messages
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.3.0 GA
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: tcunning
QA Contact:
Depends On:
Blocks: 852806 860046
TreeView+ depends on / blocked
Reported: 2012-05-08 11:48 UTC by Vinicius
Modified: 2018-11-29 21:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 852806 (view as bug list)
Last Closed:
Type: Bug

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Issue Tracker JBESB-3874 Major Closed Improve RemoteWsdlLoader error messages and logging 2018-07-31 18:47:13 UTC

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:


	~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:

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@redhat.com> updated the status of jira JBESB-3874 to Resolved

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

Note You need to log in before you can comment on or make changes to this bug.