[JBoss JIRA] (JBWS-3992) wsdl diretory is not cleaned on application deploy/undeploy thereby leaving an empty folder under "/wsdl/data" directory
by Viral Gohel (JIRA)
[ 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)
8 years, 8 months
[JBoss JIRA] (JBWS-3992) wsdl diretory is not cleaned on application deploy/undeploy thereby leaving an empty folder under "/wsdl/data" directory
by Saisha Naik (JIRA)
[ https://issues.jboss.org/browse/JBWS-3992?page=com.atlassian.jira.plugin.... ]
Saisha Naik updated JBWS-3992:
------------------------------
Steps to Reproduce:
1) Deploy sample application(attached TestEar.ear) on a fresh instance of EAP 6.4.6 domain mode.
2) Stop server via admin console or undeploy application via CLI.
Check under "../data/wsdl/" directory. The wsdl content will be removed, however the empty folder still exists.
was:
1) Deploy sample application(attached TestEar.ear) on a fresh instance of EAP 6.4.6 domain mode.
2) Stop server via admin console or undeploy application via CLI.
> 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":
> ----------------------------------------------------------------
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (JBWS-3992) wsdl diretory is not cleaned on application deploy/undeploy thereby leaving an empty folder under "/wsdl/data" directory
by Saisha Naik (JIRA)
[ https://issues.jboss.org/browse/JBWS-3992?page=com.atlassian.jira.plugin.... ]
Saisha Naik updated JBWS-3992:
------------------------------
Steps to Reproduce:
1) Deploy sample application(attached TestEar.ear) on a fresh instance of EAP 6.4.6 domain mode.
2) Stop server via admin console or undeploy application via CLI.
was:
1) Deploy sample application(attached TestEar.ear) on a fresh instance of EAP 6.4.6 domain mode.
2) Stop server via admin console or undeploy application via CLI.
The content is removed, however the empty folder still exists.
> 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":
> ----------------------------------------------------------------
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (JBWS-3992) wsdl diretory is not cleaned on application deploy/undeploy thereby leaving an empty folder under "/wsdl/data" directory
by Saisha Naik (JIRA)
[ https://issues.jboss.org/browse/JBWS-3992?page=com.atlassian.jira.plugin.... ]
Saisha Naik 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":
----------------------------------------------------------------
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.
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":
> ----------------------------------------------------------------
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (JBWS-3992) wsdl diretory is not cleaned on application deploy/undeploy thereby leaving an empty folder under "/wsdl/data" directory
by Saisha Naik (JIRA)
Saisha Naik created JBWS-3992:
---------------------------------
Summary: 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.2, jbossws-cxf-4.3
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":
----------------------------------------------------------------
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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (JBWS-3873) Web Services can't inherit a JDK8 default method
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBWS-3873?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JBWS-3873:
-----------------------------------------------
Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1196686|https://bugzilla.redhat.com/show_bug.cgi?id=1196686] from MODIFIED to POST
> Web Services can't inherit a JDK8 default method
> ------------------------------------------------
>
> Key: JBWS-3873
> URL: https://issues.jboss.org/browse/JBWS-3873
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf, jbossws-integration
> Affects Versions: jbossws-cxf-4.3.2, jbossws-cxf-5.0.0.Beta3
> Environment: JDK8
> Reporter: Jan Blizňák
> Assignee: Jim Ma
> Fix For: jbossws-cxf-5.0.1.Final, jbossws-cxf-5.1.0.Beta1
>
> Attachments: jdk8-ws-defaultmethod.zip
>
>
> Having simple SEI and POJO webservice with JDK8 feature - default method for interface:
> {code}
> @WebService
> public interface GreeterSEI {
> default public String sayHello() {
> return "Hello, Default";
> }
> }
>
> //----------------------------------------------------------
>
> @WebService
> public class GreeterImpl implements GreeterSEI {}
> {code}
> When you try to execute sayHello method:
> {code}
> Service greeterService = Service.create(...);
> GreeterSEI g = greeterService.getPort(GreeterSEI.class);
>
> Assert.assertEquals("JBoss", greeter.sayHello());
> {code}
> You will get a message-less IllegalStateException on server.
> Expected results:
> no exception, default implementation of method is invoked.
> Or if this is considered unsupported usage, the exception should be more descriptive (ie.: "Method xx not found on implementation class")
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (JBWS-3873) Web Services can't inherit a JDK8 default method
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBWS-3873?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JBWS-3873:
-----------------------------------------------
Sat6QE Jenkins <sat6-jenkins(a)redhat.com> changed the Status of [bug 1196686|https://bugzilla.redhat.com/show_bug.cgi?id=1196686] from POST to MODIFIED
> Web Services can't inherit a JDK8 default method
> ------------------------------------------------
>
> Key: JBWS-3873
> URL: https://issues.jboss.org/browse/JBWS-3873
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf, jbossws-integration
> Affects Versions: jbossws-cxf-4.3.2, jbossws-cxf-5.0.0.Beta3
> Environment: JDK8
> Reporter: Jan Blizňák
> Assignee: Jim Ma
> Fix For: jbossws-cxf-5.0.1.Final, jbossws-cxf-5.1.0.Beta1
>
> Attachments: jdk8-ws-defaultmethod.zip
>
>
> Having simple SEI and POJO webservice with JDK8 feature - default method for interface:
> {code}
> @WebService
> public interface GreeterSEI {
> default public String sayHello() {
> return "Hello, Default";
> }
> }
>
> //----------------------------------------------------------
>
> @WebService
> public class GreeterImpl implements GreeterSEI {}
> {code}
> When you try to execute sayHello method:
> {code}
> Service greeterService = Service.create(...);
> GreeterSEI g = greeterService.getPort(GreeterSEI.class);
>
> Assert.assertEquals("JBoss", greeter.sayHello());
> {code}
> You will get a message-less IllegalStateException on server.
> Expected results:
> no exception, default implementation of method is invoked.
> Or if this is considered unsupported usage, the exception should be more descriptive (ie.: "Method xx not found on implementation class")
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (JBWS-3990) Upgrade to Apache CXF 3.1.6
by Alessio Soldano (JIRA)
Alessio Soldano created JBWS-3990:
-------------------------------------
Summary: Upgrade to Apache CXF 3.1.6
Key: JBWS-3990
URL: https://issues.jboss.org/browse/JBWS-3990
Project: JBoss Web Services
Issue Type: Feature Request
Components: jbossws-cxf
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: jbossws-cxf-5.2.0.Final
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (JBWS-3808) The response-count of the endpoint metrics sometimes not counted
by Jim Ma (JIRA)
[ https://issues.jboss.org/browse/JBWS-3808?page=com.atlassian.jira.plugin.... ]
Jim Ma commented on JBWS-3808:
------------------------------
There should be an time to give the info when the metrics is last updated. This can help user understand that these metrics values is for a certain time; it could be updated at the next second. We can't add read/write lock to wait the metrics is updated completely. This will slow down performance.
> The response-count of the endpoint metrics sometimes not counted
> ----------------------------------------------------------------
>
> Key: JBWS-3808
> URL: https://issues.jboss.org/browse/JBWS-3808
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf
> Affects Versions: jbossws-cxf-4.3
> Reporter: Jim Ma
> Assignee: Jim Ma
> Fix For: jbossws-cxf-5.2.0.Final
>
>
> We now calculate the request-count, response-count and other metric value in RequestHandlerImpl , it is executed after cxf's httpDestination.invoke(cfg, context, req, response) which the response already sent to receiver and invocation is done. The response related metric won't be incremented and updated if the metric query happens between httpDestination.invoke and metrics update.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months