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.
When you deploy and undeploy application there are still data present in jboss-eap-6.2/standalone/data/wsdl directory.
Start server in first terminal
[rsvoboda@steve 620CR2]$ jboss-eap-6.2/bin/standalone.sh
deploy && undeploy in second terminal
[rsvoboda@steve 620CR2]$ jboss-eap-6.2/bin/jboss-cli.sh -c
[standalone@localhost:9999 /] deploy /home/rsvoboda/git/eap-ws-management-tests/CLIWebservicesWsdlIT.war
[standalone@localhost:9999 /] undeploy CLIWebservicesWsdlIT.war
[standalone@localhost:9999 /] quit
Stop server using Ctrl+C in first terminal
Search for war
[rsvoboda@steve 620CR2]$ find . | grep war
Is it intentional? Why would you need/want to keep wsdl data after service undeploy?
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
Setting to ON_QA since upgrade should fix this
Verified for EAP-6.3.0.ER1