Bug 1032593
Summary: | Data are kept in jboss-eap-6.2/standalone/data/wsdl after application undeploy | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Rostislav Svoboda <rsvoboda> |
Component: | Web Services | Assignee: | Rebecca Searls <rsearls> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Rostislav Svoboda <rsvoboda> |
Severity: | medium | Docs Contact: | Nidhi <nsriniva> |
Priority: | unspecified | ||
Version: | 6.2.0 | CC: | asoldano, kkhan, nobody, nsriniva, smumford |
Target Milestone: | DR0 | ||
Target Release: | EAP 6.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previous versions of JBoss EAP 6 stored data in Web Services Description Language (WSDL) directory (EAP_HOME/standalone/data/WSDL) even after an application was un-deployed from JBoss EAP server.
The WSDL data was stored as this was the default behavior as soon as an application was deployed on the server with no automated mechanism for removing the stored files.
This issue was resolved by updating files in repositories (jbossws-cxf-4.2.x and trunk) to change the behavior of maintaining and publishing WSDL logs.
The fix prevents storage of data in WSDL directory after an application is un-deployed from JBoss EAP 6.3 server.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2014-06-28 15:42:42 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: | |||
Bug Depends On: | 1061340 | ||
Bug Blocks: |
Description
Rostislav Svoboda
2013-11-20 12:51:11 UTC
There's simply never been a requirement for removing such files afair, I think they've always been left there. Upstream jira: https://issues.jboss.org/browse/JBWS-3744 https://source.jboss.org/changelog/JBossWS?cs=18156 stack-cxf-jbossws-cxf-4.2.x https://source.jboss.org/changelog/JBossWS?cs=18157 trunk Setting to ON_QA since upgrade should fix this Verified for EAP-6.3.0.ER1 |