November 2014 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3842) Cannot boot server with 2+ handlers in the same predefined configuration handler chain

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3842?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3842: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1153954|https://bugzilla.redhat.com/show_bug.cgi?id=1153954] from MODIFIED to ASSIGNED > Cannot boot server with 2+ handlers in the same predefined configuration handler chain > -------------------------------------------------------------------------------------- > > Key: JBWS-3842 > URL: https://issues.jboss.org/browse/JBWS-3842 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf, jbossws-integration > Affects Versions: jbossws-cxf-4.3 > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3.2, jbossws-cxf-5.0.0.Beta2 > > > Commit https://github.com/wildfly/wildfly/commit/e32f27d433ad3da41ef042f1ad9b950... introduced a regressions when having multiple handlers in the same handler-chain within one of the pre-defined configuration in the webservices subsystem: > {noformat} > 5:49:24,653 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.ws.endpoint-config.Recording-Endpoint-Config.pre-handler-chain.recording-handlers: org.jboss.msc.service.StartException in service jboss.ws.endpoint-config.Recording-Endpoint-Config.pre-handler-chain.recording-handlers: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_60] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_60] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_60] > Caused by: org.jboss.msc.inject.InjectionException: Value already set for this injector > at org.jboss.msc.inject.RetainingInjector.inject(RetainingInjector.java:50) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.as.webservices.dmr.ListInjector.inject(ListInjector.java:23) > at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:55) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl.doInject(ServiceControllerImpl.java:1672) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl.access$2000(ServiceControllerImpl.java:51) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.performInjections(ServiceControllerImpl.java:1917) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1876) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > ... 3 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3813) Add exception name to faultstring/detail/stackTrace

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-3813?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-3813: -------------------------------- https://issues.apache.org/jira/browse/CXF-4242 already prints the full stackTrace including the the exceptions root class and it's message. I confirmed this with CXF version (3.0.1) and wildfly-9.0.0.Alpha2-SNAPSHOT. > Add exception name to faultstring/detail/stackTrace > --------------------------------------------------- > > Key: JBWS-3813 > URL: https://issues.jboss.org/browse/JBWS-3813 > Project: JBoss Web Services > Issue Type: Enhancement > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: R Searls > Priority: Minor > Fix For: jbossws-cxf-5.0 > > > This is a placeholder for the https://issues.apache.org/jira/browse/CXF-4242 issue. We should probably have a testcase in JBWS testsuite too. > Forum reference: https://community.jboss.org/thread/198372?tstart=0&_sscc=t -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3813) Add exception name to faultstring/detail/stackTrace

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3813?page=com.atlassian.jira.plugin.... ] Alessio Soldano reopened JBWS-3813: ----------------------------------- > Add exception name to faultstring/detail/stackTrace > --------------------------------------------------- > > Key: JBWS-3813 > URL: https://issues.jboss.org/browse/JBWS-3813 > Project: JBoss Web Services > Issue Type: Enhancement > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: R Searls > Priority: Minor > Fix For: jbossws-cxf-5.0 > > > This is a placeholder for the https://issues.apache.org/jira/browse/CXF-4242 issue. We should probably have a testcase in JBWS testsuite too. > Forum reference: https://community.jboss.org/thread/198372?tstart=0&_sscc=t -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3855) Cannot boot server with 2+ handler-chains in the same predefined configuration

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3855: ------------------------------------- Summary: Cannot boot server with 2+ handler-chains in the same predefined configuration Key: JBWS-3855 URL: https://issues.jboss.org/browse/JBWS-3855 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf, jbossws-integration Affects Versions: jbossws-cxf-4.3 Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.0 This is basically the same problem described at https://issues.jboss.org/browse/JBWS-3842 but for handler-chains. It is less critical as defining multiple chains in the same configuration is not that common (and you can always merge them in a single chain). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3854) EndpointConfigAdd does not set required PropertyService dependencies

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3854: ------------------------------------- Summary: EndpointConfigAdd does not set required PropertyService dependencies Key: JBWS-3854 URL: https://issues.jboss.org/browse/JBWS-3854 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.0 In the container integration, the EndpointConfigAdd operation is not setting PropertyService dependencies on ConfigService created for endpoints. That can result in properties being lost. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3813) Add exception name to faultstring/detail/stackTrace

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-3813?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-3813: -------------------------------- Added test checking the return of a stackTrace. https://svn.jboss.org/repos/jbossws/stack/cxf/trunk (version: 5.0.0-SNAPSHOT) Committed revision 19086. > Add exception name to faultstring/detail/stackTrace > --------------------------------------------------- > > Key: JBWS-3813 > URL: https://issues.jboss.org/browse/JBWS-3813 > Project: JBoss Web Services > Issue Type: Enhancement > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: R Searls > Priority: Minor > Fix For: jbossws-cxf-5.0 > > > This is a placeholder for the https://issues.apache.org/jira/browse/CXF-4242 issue. We should probably have a testcase in JBWS testsuite too. > Forum reference: https://community.jboss.org/thread/198372?tstart=0&_sscc=t -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3560) Unlock FastInfoset feature in CXF on top of JBossAS

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3560?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3560: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1154936|https://bugzilla.redhat.com/show_bug.cgi?id=1154936] from POST to MODIFIED > Unlock FastInfoset feature in CXF on top of JBossAS > --------------------------------------------------- > > Key: JBWS-3560 > URL: https://issues.jboss.org/browse/JBWS-3560 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Reporter: Richard Opalka > Assignee: Jim Ma > Fix For: jbossws-cxf-4.2 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBWS-2680) Authentication realm name hard-coded as "EJBServiceEndpointServlet Realm"

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-2680?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-2680: --------------------------------------- Jim, your PR has been merged; is it possible to have the same fix applied to the 800 an 810 ASIL too? > Authentication realm name hard-coded as "EJBServiceEndpointServlet Realm" > ------------------------------------------------------------------------- > > Key: JBWS-2680 > URL: https://issues.jboss.org/browse/JBWS-2680 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Affects Versions: jbossws-native-3.0.5, jbossws-cxf-5.0.0.Beta1 > Environment: JBossAS 4.2.3 with JBossWS 3.0.5 > Reporter: Gerald Turner > Assignee: Jim Ma > Priority: Optional > Fix For: jbossws-cxf-5.0.0.Beta2 > > > An EJB3 endpoint defined with annotation @WebContext(authMethod="BASIC") results in JBossWS generating web.xml metadata equivalent to: > <login-config> > <auth-method>BASIC</auth-method> > <realm-name>EJBServiceEndpointServlet Realm</realm-name> > </login-config> > On one hand this is perfectly acceptable as the realm-name is just a vanity configuration parameter. However there are scenarios where it would be desirable to allow the application to override the default value: we migrated from another web services stack to JBossWS (was JAXWS-RI), some clients of our web services had explicitly configured their HTTP authentication on their end to match on realm name (one instance was Perl SOAP::Lite), quite the same way a web browser stores HTTP authentication along with the realm name such if the realm name changes, the authentication is invalidated - but since these are machines talking to each other rather than a web browser, it becomes a nightmare to debug why a client began receiving 401 errors after our upgrade. > It would be nice if the org.jboss.wsf.spi.annotation.WebContext annotation had a realmName parameter. > I attempted to work on a patch, however I'm confused by how many copies of WebAppGeneratorDeploymentAspect.java there seem to be under the jbossws/container and jbossws/framework subversion trees. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBWS-2680) Authentication realm name hard-coded as "EJBServiceEndpointServlet Realm"

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-2680?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-2680: ---------------------------------- Fix Version/s: jbossws-cxf-5.0.0.Beta2 > Authentication realm name hard-coded as "EJBServiceEndpointServlet Realm" > ------------------------------------------------------------------------- > > Key: JBWS-2680 > URL: https://issues.jboss.org/browse/JBWS-2680 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Affects Versions: jbossws-native-3.0.5, jbossws-cxf-5.0.0.Beta1 > Environment: JBossAS 4.2.3 with JBossWS 3.0.5 > Reporter: Gerald Turner > Assignee: Jim Ma > Priority: Optional > Fix For: jbossws-cxf-5.0.0.Beta2 > > > An EJB3 endpoint defined with annotation @WebContext(authMethod="BASIC") results in JBossWS generating web.xml metadata equivalent to: > <login-config> > <auth-method>BASIC</auth-method> > <realm-name>EJBServiceEndpointServlet Realm</realm-name> > </login-config> > On one hand this is perfectly acceptable as the realm-name is just a vanity configuration parameter. However there are scenarios where it would be desirable to allow the application to override the default value: we migrated from another web services stack to JBossWS (was JAXWS-RI), some clients of our web services had explicitly configured their HTTP authentication on their end to match on realm name (one instance was Perl SOAP::Lite), quite the same way a web browser stores HTTP authentication along with the realm name such if the realm name changes, the authentication is invalidated - but since these are machines talking to each other rather than a web browser, it becomes a nightmare to debug why a client began receiving 401 errors after our upgrade. > It would be nice if the org.jboss.wsf.spi.annotation.WebContext annotation had a realmName parameter. > I attempted to work on a patch, however I'm confused by how many copies of WebAppGeneratorDeploymentAspect.java there seem to be under the jbossws/container and jbossws/framework subversion trees. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBWS-2680) Authentication realm name hard-coded as "EJBServiceEndpointServlet Realm"

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-2680?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-2680: ---------------------------------- Fix Version/s: (was: jbossws-cxf-5.0) > Authentication realm name hard-coded as "EJBServiceEndpointServlet Realm" > ------------------------------------------------------------------------- > > Key: JBWS-2680 > URL: https://issues.jboss.org/browse/JBWS-2680 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Affects Versions: jbossws-native-3.0.5, jbossws-cxf-5.0.0.Beta1 > Environment: JBossAS 4.2.3 with JBossWS 3.0.5 > Reporter: Gerald Turner > Assignee: Jim Ma > Priority: Optional > > An EJB3 endpoint defined with annotation @WebContext(authMethod="BASIC") results in JBossWS generating web.xml metadata equivalent to: > <login-config> > <auth-method>BASIC</auth-method> > <realm-name>EJBServiceEndpointServlet Realm</realm-name> > </login-config> > On one hand this is perfectly acceptable as the realm-name is just a vanity configuration parameter. However there are scenarios where it would be desirable to allow the application to override the default value: we migrated from another web services stack to JBossWS (was JAXWS-RI), some clients of our web services had explicitly configured their HTTP authentication on their end to match on realm name (one instance was Perl SOAP::Lite), quite the same way a web browser stores HTTP authentication along with the realm name such if the realm name changes, the authentication is invalidated - but since these are machines talking to each other rather than a web browser, it becomes a nightmare to debug why a client began receiving 401 errors after our upgrade. > It would be nice if the org.jboss.wsf.spi.annotation.WebContext annotation had a realmName parameter. > I attempted to work on a patch, however I'm confused by how many copies of WebAppGeneratorDeploymentAspect.java there seem to be under the jbossws/container and jbossws/framework subversion trees. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 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 November 2014