Bug 1029762

Summary: Deployment of webservice with nonexisting or invalid endpoint config does not fail
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Petr Sakař <psakar>
Component: Web ServicesAssignee: Rebecca Searls <rsearls>
Status: CLOSED CURRENTRELEASE QA Contact: Rostislav Svoboda <rsvoboda>
Severity: medium Docs Contact: Russell Dickenson <rdickens>
Priority: medium    
Version: TBD EAP 6CC: asoldano, kkhan, nobody, rsvoboda
Target Milestone: DR0   
Target Release: EAP 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-28 15:38:34 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:    
Attachments:
Description Flags
diff of code changes none

Description Petr Sakař 2013-11-13 07:13:22 UTC
Description of problem:
Web Service requires end point config, which is not configured on server. Deployment containing such service should fail if the config is not defined

@org.apache.cxf.annotations.Logging(pretty=true)
@EndpointConfig(configName = "sts-config")
@javax.jws.WebService
public class TestEndpointImpl
{
  public String hello(String name)
  {
    return "Hello, " + name + "!";
  }
}

Version-Release number of selected component (if applicable):
6.2.0.CR1

How reproducible:
Always

Steps to Reproduce:
see https://bugzilla.redhat.com/show_bug.cgi?id=1021049#c13 and following comment from Alessio.


Actual results:

Deployment succeds

Expected results:

Deployment fails

Comment 1 Alessio Soldano 2013-11-13 16:25:40 UTC
I'm fine with this, upstream jira: https://issues.jboss.org/browse/JBWS-3732
This is not going to be fixed in EAP 6.2, though. Will need to move to 6.3.

Comment 2 Petr Sakař 2013-11-29 12:32:37 UTC
Additional scenario:

Endpoint config is defined but handler class is wrong - I would say it should result in deployment failure as well

Comment 4 Rebecca Searls 2013-12-10 21:27:20 UTC
Created attachment 834940 [details]
diff of code changes

Comment 6 Kabir Khan 2014-04-04 14:53:51 UTC
Setting to ON_QA since upgrade should fix this

Comment 7 Petr Sakař 2014-04-08 09:52:03 UTC
Verified for EAP-6.3.0.ER1