[JBoss JIRA] (JBWS-3904) WSDL contract retrieval enhancement and early availability check
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3904?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3904:
----------------------------------
Summary: WSDL contract retrieval enhancement and early availability check (was: WSDLcontract retrieval enhancement and early availability check)
> WSDL contract retrieval enhancement and early availability check
> ----------------------------------------------------------------
>
> Key: JBWS-3904
> …
[View More] URL: https://issues.jboss.org/browse/JBWS-3904
> Project: JBoss Web Services
> Issue Type: Enhancement
> Components: jbossws-cxf
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: jbossws-cxf-5.0
>
>
> When a contract-first endpoint references a wsdl file which is not in the expected location (for instance under META-INF instead of WEB-INF/classes/META-INF for an EJB3 WS endpoint packaged in a war deployment), the JBossWS stack might fail in resolving the wsdl, while cxf properly uses it.
> The stack needs to be able to resolve the wsdl the same as cxf and eventually early abort the deployment processing if the wsdl still can't be found.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
[View Less]
9 years, 9 months
[JBoss JIRA] (JBWS-3904) WSDLcontract retrieval enhancement and early availability check
by Alessio Soldano (JIRA)
Alessio Soldano created JBWS-3904:
-------------------------------------
Summary: WSDLcontract retrieval enhancement and early availability check
Key: JBWS-3904
URL: https://issues.jboss.org/browse/JBWS-3904
Project: JBoss Web Services
Issue Type: Enhancement
Components: jbossws-cxf
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: jbossws-cxf-5.0
When a contract-…
[View More]first endpoint references a wsdl file which is not in the expected location (for instance under META-INF instead of WEB-INF/classes/META-INF for an EJB3 WS endpoint packaged in a war deployment), the JBossWS stack might fail in resolving the wsdl, while cxf properly uses it.
The stack needs to be able to resolve the wsdl the same as cxf and eventually early abort the deployment processing if the wsdl still can't be found.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
[View Less]
9 years, 9 months
[JBoss JIRA] (JBWS-3899) Print warning for misconfigured contract-first endpoints
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3899?page=com.atlassian.jira.plugin.... ]
Alessio Soldano reopened JBWS-3899:
-----------------------------------
> 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: …
[View More]jbossws-cxf
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> 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)
[View Less]
9 years, 9 months
[JBoss JIRA] (JBWS-3899) Print warning for misconfigured contract-first endpoints
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3899?page=com.atlassian.jira.plugin.... ]
Alessio Soldano commented on JBWS-3899:
---------------------------------------
Linking to WFLY-4444 which is where this "issue" was spotted (look at my comments, the issue description is misleading).
> Print warning for misconfigured contract-first endpoints
> --------------------------------------------------------
>
> Key: JBWS-3899
> URL: https://issues.jboss.…
[View More]org/browse/JBWS-3899
> Project: JBoss Web Services
> Issue Type: Enhancement
> Components: jbossws-cxf
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> 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)
[View Less]
9 years, 9 months
[JBoss JIRA] (JBWS-3899) Print warning for misconfigured contract-first endpoints
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3899?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3899:
----------------------------------
Assignee: Alessio Soldano (was: R Searls)
Rebecca,
there're scenarios in which a missing service / port name with wsdlLocation being specified instead do not cause the deployment to fail. So the problem goes unnoticed. I've committed some changes to cover this situation.
Thanks anyway :)
> Print warning for misconfigured contract-…
[View More]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: Alessio Soldano
> 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)
[View Less]
9 years, 9 months
[JBoss JIRA] (JBWS-3899) Print warning for misconfigured contract-first endpoints
by R Searls (JIRA)
[ https://issues.jboss.org/browse/JBWS-3899?page=com.atlassian.jira.plugin.... ]
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 …
[View More]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)
[View Less]
9 years, 9 months