March 2015 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3875) Allow setting CXF features using properties on client/endpoint configs and in jboss-webservices.xml

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3875: ------------------------------------- Summary: Allow setting CXF features using properties on client/endpoint configs and in jboss-webservices.xml Key: JBWS-3875 URL: https://issues.jboss.org/browse/JBWS-3875 Project: JBoss Web Services Issue Type: Feature Request Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.0 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3874) Move JMS tests from cxf-spring-tests to cxf-tests module

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3874: ------------------------------------- Summary: Move JMS tests from cxf-spring-tests to cxf-tests module Key: JBWS-3874 URL: https://issues.jboss.org/browse/JBWS-3874 Project: JBoss Web Services Issue Type: Task Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.0 The SOAP-over-JMS tests that are currently living in the cxf-spring-tests module should be moved to the cxf-tests module as they do not need spring anymore (because of CXF changes/improvements). The recent build & testsuite re-organization also makes it easy to have a separate server configuration derived from standalone-full.xml to run these tests, without having to run the rest of module's tests on that server instance. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[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: ----------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1196686|https://bugzilla.redhat.com/show_bug.cgi?id=1196686] from ASSIGNED 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 > 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.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3846) Refactor creation process of jaxws handlers from predefined configurations

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3846?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3846: --------------------------------------- WFLY master PR: https://github.com/wildfly/wildfly/pull/7224 > Refactor creation process of jaxws handlers from predefined configurations > -------------------------------------------------------------------------- > > Key: JBWS-3846 > URL: https://issues.jboss.org/browse/JBWS-3846 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > > We currently have no special integration with the container for jaxws handlers created from a predefined client/endpoint configuration. We need to support @PostConstruct, @PreDestroy methods, as well as @EJB, @Resource and CDI injection. > Most likely this basically boils down to having AS components created for these handlers too, the same we have for jaxws handlers created after having parsed the @HandlerChain annotation. See org.jboss.as.webservices.deployers.WSIntegrationProcessorJAXWS_HANDLER and org.jboss.as.webservices.injection.WSHandlerChainAnnotationProcessor as starting point. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3846) Refactor creation process of jaxws handlers from predefined configurations

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3846?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3846: --------------------------------------- This is going to be fixed for WFLY 8.1.0 / 8.2.0 / 9.0.0 (master) integration. Won't fix for WFLY 8.0.0 due to the endpont and handler injection mechanism being different (and because of WFLY-3067 not being fixed on 8.0.0 https://github.com/wildfly/wildfly/commit/3ed595cf5ce7b605bb14925a45a9fd6... ) > Refactor creation process of jaxws handlers from predefined configurations > -------------------------------------------------------------------------- > > Key: JBWS-3846 > URL: https://issues.jboss.org/browse/JBWS-3846 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > > We currently have no special integration with the container for jaxws handlers created from a predefined client/endpoint configuration. We need to support @PostConstruct, @PreDestroy methods, as well as @EJB, @Resource and CDI injection. > Most likely this basically boils down to having AS components created for these handlers too, the same we have for jaxws handlers created after having parsed the @HandlerChain annotation. See org.jboss.as.webservices.deployers.WSIntegrationProcessorJAXWS_HANDLER and org.jboss.as.webservices.injection.WSHandlerChainAnnotationProcessor as starting point. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[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: ----------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1196686|https://bugzilla.redhat.com/show_bug.cgi?id=1196686] from NEW to ASSIGNED > 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 > 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.3.11#6341)

9 years, 9 months

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 March 2015