Bug 780455 (SOA-2884)
Summary: | Failure running SOA-P 5.1 server with space character in directory tree string | ||||||
---|---|---|---|---|---|---|---|
Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Len DiMaggio <ldimaggi> | ||||
Component: | Documentation, JBossESB, JBossWS | Assignee: | David Le Sage <dlesage> | ||||
Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 5.1.0.ER9 | CC: | kevin.conner | ||||
Target Milestone: | --- | ||||||
Target Release: | 5.2.0 GA | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
URL: | http://jira.jboss.org/jira/browse/SOA-2884 | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2011-09-30 19:46:59 UTC | 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: | |||||||
Attachments: |
|
Description
Len DiMaggio
2011-02-08 17:07:30 UTC
Link: Added: This issue is related to SOA-2482 This is not jUDDI, it is a war file provided by ESB. The war file contains an XML catalog and it is the resolution of these entries that are causing this issue. Added JBossWS as it is a bug in CXF. Attachment: Added: server.log.SOA2482.Reopen I believe this is a known bug in CXF. I could not find the corresponding JBPAPP Jira, when I do, I'll link them. Affects: Added: [Release Notes] We should document this in the installguide. Release Notes Docs Status: Added: Not Yet Documented Writer: Added: dlesage Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Known Issue Release Notes Text: Added: https://issues.jboss.org/browse/SOA-2884 The SOA Platform Server will fail if there is a space character in directory tree string. This is caused by a WAR file supplied with the ESB. The WAR file contains an XML catalogue and it is the resolution of the entries in this catalogue that causes the issue. Documented as release note. |