[
https://issues.jboss.org/browse/JBWS-3992?page=com.atlassian.jira.plugin....
]
Viral Gohel updated JBWS-3992:
------------------------------
Description:
When a web-service test EAR(having an EJB JAR/WAR inside it) is deployed in JBoss EAP, it
creates a wsdl folder inside the data directory with the name of the deployed application.
Suppose, there is an application TestEar.ear having an EJB web-service jar(MyEjb1.jar) in
it. When this application is deployed in JBoss EAP, its wsdl will be published at
`/data/wsdl/TestEar.ear/MyEjb1.jar/HelloService.wsdl`.
{code:java}
----------------------------------------------------------------
wsdl
└── TestEar.ear
└── MyEjb1.jar
└── HelloWebServiceBeanService.wsdl
----------------------------------------------------------------
{code}
When the server is stopped or the application is undeployed, the wsdl content is removed
from the location, however the folder is never deleted, thereby leaving an empty folder in
the "/data/wsdl" directory:
{code:java}
-----------------------------------------------------------------
wsdl
└── TestEar.ear
-----------------------------------------------------------------
{code}
This is not the scenario when a war/jar application is deployed individually, in which
case the content is completely removed along with the folder.
was:
When a web-service test EAR(having an EJB JAR/WAR inside it) is deployed in JBoss EAP, it
creates a wsdl folder inside the data directory with the name of the deployed application.
Suppose, there is an application TestEar.ear having an EJB web-service jar(MyEjb1.jar) in
it. When this application is deployed in JBoss EAP, its wsdl will be published at
"/data/wsdl/TestEar.ear/MyEjb1.jar/HelloService.wsdl":
----------------------------------------------------------------
wsdl
└── TestEar.ear
└── MyEjb1.jar
└── HelloWebServiceBeanService.wsdl
----------------------------------------------------------------
When the server is stopped or the application is undeployed, the wsdl content is removed
from the location, however the folder is never deleted, thereby leaving an empty folder in
the "/data/wsdl" directory:
-----------------------------------------------------------------
wsdl
└── TestEar.ear
-----------------------------------------------------------------
This is not the scenario when a war/jar application is deployed individually, in which
case the content is completely removed along with the folder.
wsdl diretory is not cleaned on application deploy/undeploy thereby
leaving an empty folder under "/wsdl/data" directory
------------------------------------------------------------------------------------------------------------------------
Key: JBWS-3992
URL:
https://issues.jboss.org/browse/JBWS-3992
Project: JBoss Web Services
Issue Type: Bug
Components: jbossws-cxf
Affects Versions: jbossws-cxf-4.3, jbossws-cxf-4.3.2
Reporter: Saisha Naik
Attachments: TestEar.ear
When a web-service test EAR(having an EJB JAR/WAR inside it) is deployed in JBoss EAP, it
creates a wsdl folder inside the data directory with the name of the deployed application.
Suppose, there is an application TestEar.ear having an EJB web-service jar(MyEjb1.jar) in
it. When this application is deployed in JBoss EAP, its wsdl will be published at
`/data/wsdl/TestEar.ear/MyEjb1.jar/HelloService.wsdl`.
{code:java}
----------------------------------------------------------------
wsdl
└── TestEar.ear
└── MyEjb1.jar
└── HelloWebServiceBeanService.wsdl
----------------------------------------------------------------
{code}
When the server is stopped or the application is undeployed, the wsdl content is removed
from the location, however the folder is never deleted, thereby leaving an empty folder in
the "/data/wsdl" directory:
{code:java}
-----------------------------------------------------------------
wsdl
└── TestEar.ear
-----------------------------------------------------------------
{code}
This is not the scenario when a war/jar application is deployed individually, in which
case the content is completely removed along with the folder.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)