April 2015 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3783) Provide full support for WS-RM 1.1 / 1.2

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3783?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3783: --------------------------------------- Tentatively scheduling for 5.1, at least CXF-4139 is done (already) > Provide full support for WS-RM 1.1 / 1.2 > ---------------------------------------- > > Key: JBWS-3783 > URL: https://issues.jboss.org/browse/JBWS-3783 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.3 > Reporter: Tadayoshi Sato > Fix For: jbossws-cxf-5.1 > > > Please provide the full implementation of WS-RM 1.1 / 1.2 in JBoss WS CXF. > According to Alessio and Jim, currently JBoss WS CXF fully supports only WS-RM 1.0 and WS-RM 1.1 is only partially available; for instance, WS-RM Policy implementation is still missing ([CXF-4139|https://issues.apache.org/jira/browse/CXF-4139]) as well as the [Securing Sequences|http://docs.oasis-open.org/ws-rx/wsrm/200608/wsrm-1.1-spec-cd-0...] support is not yet implemented in the corresponding CXF version. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3783) Provide full support for WS-RM 1.1 / 1.2

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3783?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3783: ---------------------------------- Fix Version/s: jbossws-cxf-5.1 > Provide full support for WS-RM 1.1 / 1.2 > ---------------------------------------- > > Key: JBWS-3783 > URL: https://issues.jboss.org/browse/JBWS-3783 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.3 > Reporter: Tadayoshi Sato > Fix For: jbossws-cxf-5.1 > > > Please provide the full implementation of WS-RM 1.1 / 1.2 in JBoss WS CXF. > According to Alessio and Jim, currently JBoss WS CXF fully supports only WS-RM 1.0 and WS-RM 1.1 is only partially available; for instance, WS-RM Policy implementation is still missing ([CXF-4139|https://issues.apache.org/jira/browse/CXF-4139]) as well as the [Securing Sequences|http://docs.oasis-open.org/ws-rx/wsrm/200608/wsrm-1.1-spec-cd-0...] support is not yet implemented in the corresponding CXF version. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3905) Use original thread for ejb webservice oneway operation to avoid authorization failure

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/JBWS-3905?page=com.atlassian.jira.plugin.... ] Jim Ma updated JBWS-3905: ------------------------- Summary: Use original thread for ejb webservice oneway operation to avoid authorization failure (was: Use oringial thread for ejb webserice oneway operation to avoid authorization failure) > Use original thread for ejb webservice oneway operation to avoid authorization failure > -------------------------------------------------------------------------------------- > > Key: JBWS-3905 > URL: https://issues.jboss.org/browse/JBWS-3905 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.0.0.Beta3 > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: jbossws-cxf-5.0 > > > By default, CXF's OneWayProcessorInterceptor will process the service invoker in another thread, but this causes the ejb webservice endpoint authorization failed. We need to force the orginal thread to stop this . -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3905) Use oringial thread for ejb webserice oneway operation to avoid authorization failure

by Jim Ma (JIRA)

Jim Ma created JBWS-3905: ---------------------------- Summary: Use oringial thread for ejb webserice oneway operation to avoid authorization failure Key: JBWS-3905 URL: https://issues.jboss.org/browse/JBWS-3905 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf Affects Versions: jbossws-cxf-5.0.0.Beta3 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-5.0 By default, CXF's OneWayProcessorInterceptor will process the service invoker in another thread, but this causes the ejb webservice endpoint authorization failed. We need to force the orginal thread to stop this . -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[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 > 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)

9 years

1
0
0 / 0

[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-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)

9 years

1
0
0 / 0

[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: 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)

9 years

1
0
0 / 0

[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.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)

9 years

1
0
0 / 0

[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-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)

9 years

1
0
0 / 0

[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 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)

9 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues April 2015