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)

[ https://issues.jboss.org/browse/JBWS-3875?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3875: --------------------------------------- https://docs.jboss.org/author/display/JBWS/Apache+CXF+integration#ApacheC... https://docs.jboss.org/author/display/JBWS/Apache+CXF+integration#ApacheC... > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3885) Drop Spring integration

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3885?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3885: ---------------------------------- Description: This is about dropping the Spring integration that is deprecated as described in JBWS-3884. Authoritative documentation to be fixed accordingly. was:This is about dropping the Spring integration that is deprecated as described in JBWS-3884. Affects: Documentation (Ref Guide, User Guide, etc.),Release Notes > Drop Spring integration > ----------------------- > > Key: JBWS-3885 > URL: https://issues.jboss.org/browse/JBWS-3885 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Fix For: jbossws-cxf-5.1 > > > This is about dropping the Spring integration that is deprecated as described in JBWS-3884. > Authoritative documentation to be fixed accordingly. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3885) Drop Spring integration

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3885: ------------------------------------- Summary: Drop Spring integration Key: JBWS-3885 URL: https://issues.jboss.org/browse/JBWS-3885 Project: JBoss Web Services Issue Type: Task Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Fix For: jbossws-cxf-5.1 This is about dropping the Spring integration that is deprecated as described in JBWS-3884. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3884) Deprecate Spring integration

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3884?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3884: --------------------------------------- We need to update the authoritative documentation and provide example directions on migrating applications still relying on Spring integration (e.g. using jbossws-cxf.xml descriptor) > Deprecate Spring integration > ---------------------------- > > Key: JBWS-3884 > URL: https://issues.jboss.org/browse/JBWS-3884 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > > The JBossWS integration with Spring has been evolving a lot since the initial prototype in 3.x series. WIth the latest additions in JBossWS 5 (see linked jiras), it's now time to deprecate the Spring integration, that is the ability of declaring ws endpoints and clients using spring based descriptors. This has proven to be a difficult to maintain solution and with the current stack functionalities there's really no reason for relying on it. We do have valid alternatives for configuring interceptors, features, setting WS-* options, controlling CXF internals, performing injection into EE components, etc. > In any case, the Spring integration has been disabled by default (optionally turned on by manually installing spring module on the container) since JBoss AS 7 series and users should now be properly relying on plain JAX-WS whenever possible and using WS-Policy and JBossWS configuration properties for advanced WS-* functionalities, so this is not going to be that an issue to the majority of the user base. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3884) Deprecate Spring integration

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3884?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3884: ---------------------------------- Description: The JBossWS integration with Spring has been evolving a lot since the initial prototype in 3.x series. WIth the latest additions in JBossWS 5 (see linked jiras), it's now time to deprecate the Spring integration, that is the ability of declaring ws endpoints and clients using spring based descriptors. This has proven to be a difficult to maintain solution and with the current stack functionalities there's really no reason for relying on it. We do have valid alternatives for configuring interceptors, features, setting WS-* options, controlling CXF internals, performing injection into EE components, etc. In any case, the Spring integration has been disabled by default (optionally turned on by manually installing spring module on the container) since JBoss AS 7 series and users should now be properly relying on plain JAX-WS whenever possible and using WS-Policy and JBossWS configuration properties for advanced WS-* functionalities, so this is not going to be that an issue to the majority of the user base. was: The JBossWS integration with Spring has been evolving a lot since the initial prototype in 3.x series. WIth the latest additions in JBossWS 5 (see linked jiras), it's now time to deprecate the Spring integration, that is the ability of declaring ws endpoints and clients using spring based descriptors. This has proven to be a difficult to maintain solution and with the current stack functionalities there's really no reason for relying on it. We do have valid alternatives for configuring interceptors, features, setting WS-* options, controlling CXF internals, performing injection into EE components, etc. In any case, the Spring integration has been disabled by default (optionally turned on by manually installing spring module on the container) since JBoss AS 7 series and users should now be properly relying on plain JAX-WS whenever possible and using WS-Policy and JBossWS configuration properties for advanced WS-* functionalities. > Deprecate Spring integration > ---------------------------- > > Key: JBWS-3884 > URL: https://issues.jboss.org/browse/JBWS-3884 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > > The JBossWS integration with Spring has been evolving a lot since the initial prototype in 3.x series. WIth the latest additions in JBossWS 5 (see linked jiras), it's now time to deprecate the Spring integration, that is the ability of declaring ws endpoints and clients using spring based descriptors. This has proven to be a difficult to maintain solution and with the current stack functionalities there's really no reason for relying on it. We do have valid alternatives for configuring interceptors, features, setting WS-* options, controlling CXF internals, performing injection into EE components, etc. > In any case, the Spring integration has been disabled by default (optionally turned on by manually installing spring module on the container) since JBoss AS 7 series and users should now be properly relying on plain JAX-WS whenever possible and using WS-Policy and JBossWS configuration properties for advanced WS-* functionalities, so this is not going to be that an issue to the majority of the user base. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3884) Deprecate Spring integration

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3884: ------------------------------------- Summary: Deprecate Spring integration Key: JBWS-3884 URL: https://issues.jboss.org/browse/JBWS-3884 Project: JBoss Web Services Issue Type: Task Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.0 The JBossWS integration with Spring has been evolving a lot since the initial prototype in 3.x series. WIth the latest additions in JBossWS 5 (see linked jiras), it's now time to deprecate the Spring integration, that is the ability of declaring ws endpoints and clients using spring based descriptors. This has proven to be a difficult to maintain solution and with the current stack functionalities there's really no reason for relying on it. We do have valid alternatives for configuring interceptors, features, setting WS-* options, controlling CXF internals, performing injection into EE components, etc. In any case, the Spring integration has been disabled by default (optionally turned on by manually installing spring module on the container) since JBoss AS 7 series and users should now be properly relying on plain JAX-WS whenever possible and using WS-Policy and JBossWS configuration properties for advanced WS-* functionalities. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3834) ant tasks should include a clear help target

by Roberto Polli (JIRA)

[ https://issues.jboss.org/browse/JBWS-3834?page=com.atlassian.jira.plugin.... ] Roberto Polli commented on JBWS-3834: ------------------------------------- Great new! Farewell ant, you served well (maybe) :P Peace, R. > ant tasks should include a clear help target > -------------------------------------------- > > Key: JBWS-3834 > URL: https://issues.jboss.org/browse/JBWS-3834 > Project: JBoss Web Services > Issue Type: Enhancement > Components: jbossws-cxf > Environment: all > Reporter: Roberto Polli > Assignee: Alessio Soldano > Priority: Optional > Labels: documentation > > I could have sense that: > 1- default target is an help screen > running #ant > you'll see a brief description of how to run/deploy the tests. > A copy/paste example instructions are a plus ;) > 2- ant provides an "help" task > running #ant help > you'll see the forementioned screen > A sample patch http://fpaste.org/136684/23459141/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3759) Bug in schemalocation for swaref for Jboss EAP 6.2

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3759?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3759: ---------------------------------- Attachment: soaptest.war soaptest.zip Attached referenced archives for reproducing the issue. > Bug in schemalocation for swaref for Jboss EAP 6.2 > -------------------------------------------------- > > Key: JBWS-3759 > URL: https://issues.jboss.org/browse/JBWS-3759 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.3 > Reporter: Richard Borge > Assignee: R Searls > Priority: Minor > Labels: cxf, eap-6.2 > Attachments: soaptest.war, soaptest.zip > > > I am using Jboss EAP-6.2 for a SOAP service which uses the Datahandler to handle returned streams. In the WSDL, I am expecting the xsd for swaref to be imported, but the schemalocation gets messed up. Instead of "http://ws-i.org/profiles/basic/1.1/swaref.xsd" I get "http://localhost:8080/soaptest/mys?xsd=http://ws-i.org/profiles/basic/1.1...". This is a bit of a problem because, among other things, it messes up soapUI for thos of our customers that want to test the service. > I have tried to look through the jboss code, but it is very hard to find where the localhost-part gets concatenated onto the swaref XSD. > The source code: > http://folk.uio.no/richared/jboss/soaptest.zip -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3824) "Input line is too long" when running wsprovide in fork mode on Windows

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3824?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3824: ---------------------------------- Fix Version/s: jbossws-jaxws-tools-maven-plugin-1.2.0.Beta1 > "Input line is too long" when running wsprovide in fork mode on Windows > ----------------------------------------------------------------------- > > Key: JBWS-3824 > URL: https://issues.jboss.org/browse/JBWS-3824 > Project: JBoss Web Services > Issue Type: Bug > Components: jaxws-tools-maven-plugin > Affects Versions: jbossws-jaxws-tools-maven-plugin-1.1.2.Final > Reporter: Alessio Soldano > Assignee: R Searls > Fix For: jbossws-jaxws-tools-maven-plugin-1.2.0.Beta1 > > > When running the tools in fork mode on Windows OS, we can end up building a command line which is too long. > We should prevent this by using a pathing jar solution, similarly to what Surefire plugin does (a jar with manifest pointing to the actual dependency jars). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3873) Web Services can't inherit a JDK8 default method

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3873?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3873: ---------------------------------- Fix Version/s: jbossws-cxf-5.0 > 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 > Fix For: jbossws-cxf-5.0 > > 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, 8 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