January 2014 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3711) Refactor exising tests to use ShrinkWrap

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3711?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3711: ---------------------------------- Fix Version/s: jbossws-cxf-4.4 (was: jbossws-cxf-4.3) > Refactor exising tests to use ShrinkWrap > ---------------------------------------- > > Key: JBWS-3711 > URL: https://issues.jboss.org/browse/JBWS-3711 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Fix For: jbossws-cxf-4.4 > > > See JBWS-3667, we should refactor the existing tests (some of them? all?) to use ShrinkWrap for building deployment archives. > Also check comment at https://issues.jboss.org/browse/JBWS-3667?focusedCommentId=12801222&page=... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3383) WS-sec truststore/keystore urls should be obtained from the central security configuration

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3383?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3383: ---------------------------------- Fix Version/s: jbossws-cxf-4.4 (was: jbossws-cxf-4.3) > WS-sec truststore/keystore urls should be obtained from the central security configuration > ------------------------------------------------------------------------------------------ > > Key: JBWS-3383 > URL: https://issues.jboss.org/browse/JBWS-3383 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Richard Opalka > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.4 > > > Anil Saldhana wrote on https://github.com/jbossas/jboss-as/pull/630 : > Ensure that the ws-sec truststore/keystore urls are obtained from the central security configuration. > Rely on the from https://docs.jboss.org/author/display/AS7/Security+subsystem+configuration > Pull req 630 was actually closed and later replaced by https://github.com/jbossas/jboss-as/pull/662 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3670) Spring declared endpoints, AS components and injection

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3670?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3670: --------------------------------------- Jim, are the WFLY changes required for this in https://github.com/jimma/wildfly/tree/JBWS-3670 ? If the changes are backward compatible with JBossWS 4.2.x, can you send a PR against WFLY master? > Spring declared endpoints, AS components and injection > ------------------------------------------------------ > > Key: JBWS-3670 > URL: https://issues.jboss.org/browse/JBWS-3670 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Jim Ma > Fix For: jbossws-cxf-4.3 > > > See https://community.jboss.org/message/822796#822796 . Basically the user is trying to declare a WS endpoint using Spring configuration and having other Spring beans injected in it. The problem is the endpoint is actually being created as an AS component later after the spring context has already been built. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3753) Improve destination matching when processing requests

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3753?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3753: --------------------------------------- https://issues.apache.org/jira/browse/CXF-5523 > Improve destination matching when processing requests > ----------------------------------------------------- > > Key: JBWS-3753 > URL: https://issues.jboss.org/browse/JBWS-3753 > Project: JBoss Web Services > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > Each time a SOAP request message is processed, the proper destination among those available in the Bus associated to the ws application has to be selected. Currently, we iterate over all destinations to find one that matches the requested path. We could improve this by trying looking up the destination in a map (path->destination) and fall back to iteration only if no exact match is possible (for instance because the proper endpoint has been declared with a "/*" url-pattern in web.xml). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3748) Wildfly 8 ws-security client throws exception

by Joseph Hwang (JIRA)

[ https://issues.jboss.org/browse/JBWS-3748?page=com.atlassian.jira.plugin.... ] Joseph Hwang updated JBWS-3748: ------------------------------- Fix Version/s: jbossws-cxf-4.4 (was: jbossws-cxf-4.3) > Wildfly 8 ws-security client throws exception > --------------------------------------------- > > Key: JBWS-3748 > URL: https://issues.jboss.org/browse/JBWS-3748 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: Joseph Hwang > Fix For: jbossws-cxf-4.4 > > Attachments: WSSHelloWorld.zip > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3748) Wildfly 8 ws-security client throws exception

by Joseph Hwang (JIRA)

[ https://issues.jboss.org/browse/JBWS-3748?page=com.atlassian.jira.plugin.... ] Joseph Hwang updated JBWS-3748: ------------------------------- Fix Version/s: jbossws-cxf-4.3 > Wildfly 8 ws-security client throws exception > --------------------------------------------- > > Key: JBWS-3748 > URL: https://issues.jboss.org/browse/JBWS-3748 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: Joseph Hwang > Fix For: jbossws-cxf-4.3 > > Attachments: WSSHelloWorld.zip > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3753) Improve destination matching when processing requests

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3753: ------------------------------------- Summary: Improve destination matching when processing requests Key: JBWS-3753 URL: https://issues.jboss.org/browse/JBWS-3753 Project: JBoss Web Services Issue Type: Enhancement Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.3 Each time a SOAP request message is processed, the proper destination among those available in the Bus associated to the ws application has to be selected. Currently, we iterate over all destinations to find one that matches the requested path. We could improve this by trying looking up the destination in a map (path->destination) and fall back to iteration only if no exact match is possible (for instance because the proper endpoint has been declared with a "/*" url-pattern in web.xml). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3752) Upgrade to Apache CXF 2.7.9

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3752: ------------------------------------- Summary: Upgrade to Apache CXF 2.7.9 Key: JBWS-3752 URL: https://issues.jboss.org/browse/JBWS-3752 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-4.3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3738) Expand WS-Trust / STS test coverage and documentation

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-3738?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-3738: -------------------------------- Filed following jiras in CXF against WS-trust extentions ActAs and OnBehalfOf - https://issues.apache.org/jira/browse/CXF-5518 Setting SecurityConstants.STS_TOKEN_ACT_AS as string improper handling - https://issues.apache.org/jira/browse/CXF-5519 Setting SecurityConstants.STS_TOKEN_ACT_AS as CallbackHander requires better documentation. - https://issues.apache.org/jira/browse/CXF-5520 Setting SecurityConstants.STS_TOKEN_ON_BEHALF_OF as string improper handling - https://issues.apache.org/jira/browse/CXF-5521 Setting SecurityConstants.STS_TOKEN_ON_BEHALF_OF as CallbackHander requires better documentation. > Expand WS-Trust / STS test coverage and documentation > ----------------------------------------------------- > > Key: JBWS-3738 > URL: https://issues.jboss.org/browse/JBWS-3738 > Project: JBoss Web Services > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: R Searls > Fix For: jbossws-cxf-4.3 > > > We should possibly cover more WS-Trust/STS scenarios in the testsuite (different SAML tokens, etc.) and expand the documentation accordingly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3722) jbossws-cxf-client is using 2.1 version of jaxb-impl

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/JBWS-3722?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda commented on JBWS-3722: ----------------------------------------- [~asoldano] could you please merge this change to 4.2.x branch too ? > jbossws-cxf-client is using 2.1 version of jaxb-impl > ---------------------------------------------------- > > Key: JBWS-3722 > URL: https://issues.jboss.org/browse/JBWS-3722 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.1 > Reporter: Rostislav Svoboda > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > Invoking dependency:tree on POM looking like this: > {code} > <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> > <modelVersion>4.0.0</modelVersion> > <name>JBoss Web Services - Client test</name> > <groupId>org.jboss.ws.cxf</groupId> > <artifactId>jbossws-cxf-client-test</artifactId> > <version>1.0.0.Final</version> > <properties> > <jbossws-cxf-client-version>4.2.1.Final</jbossws-cxf-client-version> > </properties> > <dependencies> > <dependency> > <groupId>org.jboss.ws.cxf</groupId> > <artifactId>jbossws-cxf-client</artifactId> > <version>${jbossws-cxf-client-version}</version> > </dependency> > </dependencies> > </project> > {code} > jaxb-impl dependency should be 2.2.x > {code} > ... > +- org.apache.cxf:cxf-rt-transports-jms:jar:2.7.6:compile > | +- org.apache.cxf:cxf-rt-management:jar:2.7.6:compile > | +- com.sun.xml.bind:jaxb-impl:jar:2.1.13:compile > | \- com.sun.xml.bind:jaxb-xjc:jar:2.1.13:compile > ... > {code} > Info from IRC: > <asoldano> rsvoboda, I think the situation here is complicated by multiple dependency management block existing (both in cxf parent and jbossws-cxf parent) and missing explicit dependency to jaxb-impl in jbossws-cxf-client pom. I need to check the actual order of dependencyManagement processing in Maven impl, perhaps it's processed in a different order then we expect -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 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 January 2014