-
Bug
-
Resolution: Done
-
Minor
-
EAP_EWP 5.1.0
-
None
-
Workaround Exists
-
-
The logging level for MessageContextJAXWS was too high when the conversion of a WSDL URL to a URI failed. This caused excessive log messages. The logging level for these messages has been lowered to reflect the true severity.
-
Documented as Resolved Issue
The following is logged as endpoints are called when JBoss EAP is installed to a folder containing spaces: -
MessageContextJAXWS] [WARN] Cannot get the wsdl url
java.net.URISyntaxException: Illegal character in path at index 16: file:/C:/Program Files/jboss/server/default/data/wsdl/10500SomeAdmin.jar/MyService6029401450925031236.wsdl
at java.net.URI$Parser.fail(Unknown Source)
at java.net.URI$Parser.checkChars(Unknown Source)
at java.net.URI$Parser.parseHierarchical(Unknown Source)
at java.net.URI$Parser.parse(Unknown Source)
at java.net.URI.<init>(Unknown Source)
at java.net.URL.toURI(Unknown Source)
at org.jboss.ws.core.jaxws.handler.MessageContextJAXWS.setOperationMetaData(MessageContextJAXWS.java:140)
- blocks
-
JBPAPP-4552 Release and upgrade JBossWS Native
- Closed
- incorporates
-
JBWS-3183 Reduce Logging Level for MessageContextJAXWS when WSDL URL fails conversion to URI
- Closed
- is cloned by
-
JBPAPP-5258 JBossWS Native - Reduce Logging Level for MessageContextJAXWS when WSDL URL fails conversion to URI
- Closed