Bug 819852 - Improving SOAPProxy classpath protocol logging messages
Summary: Improving SOAPProxy classpath protocol logging messages
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.3.0 GA
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: tcunning
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 852806 860046
TreeView+ depends on / blocked
 
Reported: 2012-05-08 11:48 UTC by Vinicius
Modified: 2025-02-10 03:19 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
: 852806 (view as bug list)
Environment:
Last Closed: 2025-02-10 03:19:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBESB-3874 0 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:

      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

Comment 4 Red Hat Bugzilla 2025-02-10 03:19:47 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


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