[jbossws-issues] [JBoss JIRA] (JBWS-3899) Print warning for misconfigured contract-first endpoints

[R Searls (JIRA)]

    [ https://issues.jboss.org/browse/JBWS-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059299#comment-13059299 ] 

R Searls commented on JBWS-3899:
--------------------------------

The @WebService annotation is processed in
org.jboss.wsf.stack.cxf.metadata.MetadataBuilder#createDDEndpoint.
Values are set for each attribute whether or not the user has defined
a value.  When the attribute serviceName is not defined the classname+Service
is defined for it.

It is possible to have a scenario in which the @WebService attributes are defined
such that they are different from what is declared in the wsdl (i.e. wsdl:service, 
wsdl:port).  The app would also fail to deploy in this case.
The server log reports a deployment error for such a scenario.  It does not identify
the cause as differing definitions.  The question becomes do we add code to check 
for and report this specific failure scenario or is the current handling sufficient?


> Print warning for misconfigured contract-first endpoints
> --------------------------------------------------------
>
>                 Key: JBWS-3899
>                 URL: https://issues.jboss.org/browse/JBWS-3899
>             Project: JBoss Web Services
>          Issue Type: Enhancement
>          Components: jbossws-cxf
>            Reporter: Alessio Soldano
>            Assignee: R Searls
>            Priority: Minor
>             Fix For: jbossws-cxf-5.0
>
>
> When user provides misconfigured contract-first endpoints as below, the stack silently ignore the request of using the specified contract and generates the wsdl (code-first).
> {noformat}
> @Stateless
> @WebService(portName = "SimpleEchoPort",wsdlLocation = "META-INF/wsdl/Echo.wsdl")
> public class SimpleEcho {
> ...
> }
> {noformat}
> (notice there's no serviceName specified, hence the stack won't know which port/service to use from the contract)
> We should likely print a warning in this scenario, asking the user if he really wants a contract-first endpoint.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)