February 2017 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-4059) Support CXF FaultListener

by 华绪吴 (JIRA)

华绪吴 created JBWS-4059: -------------------------- Summary: Support CXF FaultListener Key: JBWS-4059 URL: https://issues.jboss.org/browse/JBWS-4059 Project: JBoss Web Services Issue Type: Feature Request Components: jbossws-cxf Affects Versions: jbossws-cxf-5.1.3.Final Reporter: 华绪吴 Priority: Optional Attachments: Support_CXF_FaultListener.patch with this feature, developer can hide runtime exception warn logging and custom the runtime exception output instead of mapping to a relatively generice soap:fault which was send to client. I created a patch for jbossws-cxf-5.1.3.Final. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4058) Upgrade to Apache CXF 3.1.10

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-4058: ------------------------------------- Summary: Upgrade to Apache CXF 3.1.10 Key: JBWS-4058 URL: https://issues.jboss.org/browse/JBWS-4058 Project: JBoss Web Services Issue Type: Component Upgrade Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.1.8.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4052) Maven build is unnecessarily updating org.eclipse.* dependencies everytime

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-4052?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-4052: ---------------------------------- Fix Version/s: jbossws-cxf-5.1.8.Final (was: jbossws-cxf-5.2.0.Final) > Maven build is unnecessarily updating org.eclipse.* dependencies everytime > -------------------------------------------------------------------------- > > Key: JBWS-4052 > URL: https://issues.jboss.org/browse/JBWS-4052 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf, productization > Affects Versions: jbossws-cxf-5.1.7.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Minor > Fix For: jbossws-cxf-5.1.8.Final > > > Maven build is unnecessarily updating org.eclipse.* dependencies everytime which could prolong the execution by several minutes just to wait for connections to timeout (depending on current environment setup). > {code:java} > [INFO] Scanning for projects... > Downloading: http://snapshots.jboss.org/maven2/org/eclipse/wst/css/core/maven-metadata... > Downloading: http://repository.jboss.com/maven2/org/eclipse/wst/css/core/maven-metadat... > [WARNING] Could not transfer metadata org.eclipse.wst.css:core/maven-metadata.xml from/to repository.jboss.com (http://repository.jboss.com/maven2/): Connect to repository.jboss.com:80 [repository.jboss.com/10.5.105.13] failed: Connection timed out (Connection timed out) > [WARNING] Could not transfer metadata org.eclipse.wst.css:core/maven-metadata.xml from/to maven-repository.dev.java.net (http://download.java.net/maven/1): Cannot access http://download.java.net/maven/1 with type legacy using the available connector factories: BasicRepositoryConnectorFactory > Downloading: http://repository.jboss.com/maven2/org/eclipse/wst/sse/core/maven-metadat... > Downloading: http://snapshots.jboss.org/maven2/org/eclipse/wst/sse/core/maven-metadata... > [WARNING] Could not transfer metadata org.eclipse.wst.sse:core/maven-metadata.xml from/to repository.jboss.com (http://repository.jboss.com/maven2/): Connect to repository.jboss.com:80 [repository.jboss.com/10.5.105.13] failed: Connection timed out (Connection timed out) > [WARNING] Could not transfer metadata org.eclipse.wst.sse:core/maven-metadata.xml from/to maven-repository.dev.java.net (http://download.java.net/maven/1): Cannot access http://download.java.net/maven/1 with type legacy using the available connector factories: BasicRepositoryConnectorFactory > Downloading: http://repository.jboss.com/maven2/org/eclipse/wst/common/uriresolver/mav... > Downloading: http://snapshots.jboss.org/maven2/org/eclipse/wst/common/uriresolver/mave... > [WARNING] Could not transfer metadata org.eclipse.wst.common:uriresolver/maven-metadata.xml from/to repository.jboss.com (http://repository.jboss.com/maven2/): Connect to repository.jboss.com:80 [repository.jboss.com/10.5.105.13] failed: Connection timed out (Connection timed out) > [WARNING] Could not transfer metadata org.eclipse.wst.common:uriresolver/maven-metadata.xml from/to maven-repository.dev.java.net (http://download.java.net/maven/1): Cannot access http://download.java.net/maven/1 with type legacy using the available connector factories: BasicRepositoryConnectorFactory > [WARNING] Failure to transfer org.eclipse.wst.sse:core/maven-metadata.xml from http://repository.jboss.com/maven2/ was cached in the local repository, resolution will not be reattempted until the update interval of repository.jboss.com has elapsed or updates are forced. Original error: Could not transfer metadata org.eclipse.wst.sse:core/maven-metadata.xml from/to repository.jboss.com (http://repository.jboss.com/maven2/): Connect to repository.jboss.com:80 [repository.jboss.com/10.5.105.13] failed: Connection timed out (Connection timed out) > [WARNING] Failure to transfer org.eclipse.wst.sse:core/maven-metadata.xml from http://download.java.net/maven/1 was cached in the local repository, resolution will not be reattempted until the update interval of maven-repository.dev.java.net has elapsed or updates are forced. Original error: Could not transfer metadata org.eclipse.wst.sse:core/maven-metadata.xml from/to maven-repository.dev.java.net (http://download.java.net/maven/1): Cannot access http://download.java.net/maven/1 with type legacy using the available connector factories: BasicRepositoryConnectorFactory > [INFO] ------------------------------------------------------------------------ > {code} > This is caused by issue with maven-jdocbook-plugin PRESSGANG-60. > There are two basic solutions to this: > # only exclude org.eclipse.* dependencies in plugin dependency management since they are not used anyway (info from the PRESSGANG-60) > # do a full update of maven-jdocbook-plugin to latest version along with usage of new org.jboss.pressgang extensions instead of current org.jboss:jbossorg-jdocbook* ones -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4057) How to use sessionTransacted attribute in jbossws.

by Saisha Naik (JIRA)

[ https://issues.jboss.org/browse/JBWS-4057?page=com.atlassian.jira.plugin.... ] Saisha Naik updated JBWS-4057: ------------------------------ Summary: How to use sessionTransacted attribute in jbossws. (was: How to use sessionTransacted in jbossws.) > How to use sessionTransacted attribute in jbossws. > -------------------------------------------------- > > Key: JBWS-4057 > URL: https://issues.jboss.org/browse/JBWS-4057 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.0 > Reporter: Saisha Naik > Attachments: cxf-eap-jms-redelivery.war.tar.xz > > > Is is possible to use 'sessionTransacted' attribute in JBossws? 'sessionTransacted' as described in http://cxf.apache.org/docs/jms-transactions.html can be configured on the endpoint normally and CXF will then roll back the message on if any exception happens. So, in this case say a message should be retried by 5 times before it goes to the queue. > Apache CXF does mention the use of 'sessionTransacted' in their docs, but it would be great if there can be an example in JbossWS to have some point of reference. Attached is a sample application for reference which will need spring as well as activemq modules installed in EAP. . -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4057) How to use sessionTransacted in jbossws.

by Saisha Naik (JIRA)

[ https://issues.jboss.org/browse/JBWS-4057?page=com.atlassian.jira.plugin.... ] Saisha Naik updated JBWS-4057: ------------------------------ Security: (was: Red Hat Customer) > How to use sessionTransacted in jbossws. > ---------------------------------------- > > Key: JBWS-4057 > URL: https://issues.jboss.org/browse/JBWS-4057 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.0 > Reporter: Saisha Naik > Attachments: cxf-eap-jms-redelivery.war.tar.xz > > > Is is possible to use 'sessionTransacted' attribute in JBossws? 'sessionTransacted' as described in http://cxf.apache.org/docs/jms-transactions.html can be configured on the endpoint normally and CXF will then roll back the message on if any exception happens. So, in this case say a message should be retried by 5 times before it goes to the queue. > Apache CXF does mention the use of 'sessionTransacted' in their docs, but it would be great if there can be an example in JbossWS to have some point of reference. Attached is a sample application for reference which will need spring as well as activemq modules installed in EAP. . -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4056) Ensure all tests are written junit4 way

by Jan Blizňák (JIRA)

[ https://issues.jboss.org/browse/JBWS-4056?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4056: ------------------------------ Assignee: Jan Blizňák > Ensure all tests are written junit4 way > --------------------------------------- > > Key: JBWS-4056 > URL: https://issues.jboss.org/browse/JBWS-4056 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.7.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > > Currently most of the tests in JBWS project are written using @RunWith(Arquillian.class) whereas there are others extending TestCase class from junit framework. The latter is the junit3 way of writing tests which relies on test method name convention. > Furthermore, almost all tests transitively extends TestCase via JBossWSTest despite of using @RunWith. In some cases that leads to situations where some test methods are actually skipped because they miss @Test annotation, which were probably missed within migration to Arquillian. > We should ensure all tests are annotated with @Test. We also should remove inheritance from TestCase class and instead use Assert.* methods directly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4056) Ensure all tests are written junit4 way

by Jan Blizňák (JIRA)

[ https://issues.jboss.org/browse/JBWS-4056?page=com.atlassian.jira.plugin.... ] Jan Blizňák commented on JBWS-4056: ----------------------------------- Sorry about that, I missed that usage since they are looked up by FQDN class name in String. Anyway I sent a proposal PR https://github.com/jbossws/jbossws-cxf/pull/23, could you have a look? > Ensure all tests are written junit4 way > --------------------------------------- > > Key: JBWS-4056 > URL: https://issues.jboss.org/browse/JBWS-4056 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.7.Final > Reporter: Jan Blizňák > > Currently most of the tests in JBWS project are written using @RunWith(Arquillian.class) whereas there are others extending TestCase class from junit framework. The latter is the junit3 way of writing tests which relies on test method name convention. > Furthermore, almost all tests transitively extends TestCase via JBossWSTest despite of using @RunWith. In some cases that leads to situations where some test methods are actually skipped because they miss @Test annotation, which were probably missed within migration to Arquillian. > We should ensure all tests are annotated with @Test. We also should remove inheritance from TestCase class and instead use Assert.* methods directly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4056) Ensure all tests are written junit4 way

by Jan Blizňák (JIRA)

[ https://issues.jboss.org/browse/JBWS-4056?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4056: ------------------------------ Description: Currently most of the tests in JBWS project are written using @RunWith(Arquillian.class) whereas there are others extending TestCase class from junit framework. The latter is the junit3 way of writing tests which relies on test method name convention. Furthermore, almost all tests transitively extends TestCase via JBossWSTest despite of using @RunWith. In some cases that leads to situations where some test methods are actually skipped because they miss @Test annotation, which were probably missed within migration to Arquillian. We should ensure all tests are annotated with @Test. We also should remove inheritance from TestCase class and instead use Assert.* methods directly. was: Currently most of the tests in JBWS project are written using @RunWith(Arquillian.class) whereas there are others extending TestCase class from junit framework. The latter is the junit3 way of writing tests which relies on test method name convention. Furthermore, almost all tests transitively extends TestCase via JBossWSTest despite of using @RunWith. In some cases that leads to situations where some test methods are actually skipped because they miss @Test annotation, which were probably missed within migration to Arquillian. We should ensure all tests use junit4 runners, ie. either @RunWith(JUnit4.class) or @RunWith(Arquillian.class). We also should remove inheritance from TestCase class and instead use Assert.* methods directly. > Ensure all tests are written junit4 way > --------------------------------------- > > Key: JBWS-4056 > URL: https://issues.jboss.org/browse/JBWS-4056 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.7.Final > Reporter: Jan Blizňák > > Currently most of the tests in JBWS project are written using @RunWith(Arquillian.class) whereas there are others extending TestCase class from junit framework. The latter is the junit3 way of writing tests which relies on test method name convention. > Furthermore, almost all tests transitively extends TestCase via JBossWSTest despite of using @RunWith. In some cases that leads to situations where some test methods are actually skipped because they miss @Test annotation, which were probably missed within migration to Arquillian. > We should ensure all tests are annotated with @Test. We also should remove inheritance from TestCase class and instead use Assert.* methods directly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4056) Ensure all tests are written junit4 way

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-4056?page=com.atlassian.jira.plugin.... ] Alessio Soldano edited comment on JBWS-4056 at 2/8/17 11:48 AM: ---------------------------------------------------------------- The WSConsumerPlugin and WSProviderPlugin are not meant to be executed directly as tests. They're loaded by WSConsumerTestCaseForked and WSProviderTestCaseForked to workaround classloading issues that would prevent proper testing. was (Author: asoldano): The WSConsumerPlugin and WSProviderPlugin are not meant to executed directly as tests. They're loaded by WSConsumerTestCaseForked and WSProviderTestCaseForked to workaround classloading issues that would prevent proper testing. > Ensure all tests are written junit4 way > --------------------------------------- > > Key: JBWS-4056 > URL: https://issues.jboss.org/browse/JBWS-4056 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.7.Final > Reporter: Jan Blizňák > > Currently most of the tests in JBWS project are written using @RunWith(Arquillian.class) whereas there are others extending TestCase class from junit framework. The latter is the junit3 way of writing tests which relies on test method name convention. > Furthermore, almost all tests transitively extends TestCase via JBossWSTest despite of using @RunWith. In some cases that leads to situations where some test methods are actually skipped because they miss @Test annotation, which were probably missed within migration to Arquillian. > We should ensure all tests use junit4 runners, ie. either @RunWith(JUnit4.class) or @RunWith(Arquillian.class). We also should remove inheritance from TestCase class and instead use Assert.* methods directly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4056) Ensure all tests are written junit4 way

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-4056?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-4056: --------------------------------------- The WSConsumerPlugin and WSProviderPlugin are not meant to executed directly as tests. They're loaded by WSConsumerTestCaseForked and WSProviderTestCaseForked to workaround classloading issues that would prevent proper testing. > Ensure all tests are written junit4 way > --------------------------------------- > > Key: JBWS-4056 > URL: https://issues.jboss.org/browse/JBWS-4056 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.7.Final > Reporter: Jan Blizňák > > Currently most of the tests in JBWS project are written using @RunWith(Arquillian.class) whereas there are others extending TestCase class from junit framework. The latter is the junit3 way of writing tests which relies on test method name convention. > Furthermore, almost all tests transitively extends TestCase via JBossWSTest despite of using @RunWith. In some cases that leads to situations where some test methods are actually skipped because they miss @Test annotation, which were probably missed within migration to Arquillian. > We should ensure all tests use junit4 runners, ie. either @RunWith(JUnit4.class) or @RunWith(Arquillian.class). We also should remove inheritance from TestCase class and instead use Assert.* methods directly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 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 February 2017