August 2013 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3688) Upgrade to Apache CXF 2.7.7

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3688: ------------------------------------- Summary: Upgrade to Apache CXF 2.7.7 Key: JBWS-3688 URL: https://issues.jboss.org/browse/JBWS-3688 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-4.2.1 -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3687) Intermittent failures caused by JBWS1178TestCase

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3687: ------------------------------------- Summary: Intermittent failures caused by JBWS1178TestCase Key: JBWS-3687 URL: https://issues.jboss.org/browse/JBWS-3687 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, productization Reporter: Alessio Soldano Fix For: jbossws-cxf-4.2.1 JBWS1178TestCase can't be executed together with other tests as it modifies the server configuration. It must be turned into a Forked testcase. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3686) Upgrade to Apache CXF 3.0.0

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3686?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3686: ---------------------------------- Description: http://cxf.apache.org/docs/30-migration-guide.html > Upgrade to Apache CXF 3.0.0 > --------------------------- > > Key: JBWS-3686 > URL: https://issues.jboss.org/browse/JBWS-3686 > 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 > > > http://cxf.apache.org/docs/30-migration-guide.html -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3686) Upgrade to Apache CXF 3.0.0

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3686: ------------------------------------- Summary: Upgrade to Apache CXF 3.0.0 Key: JBWS-3686 URL: https://issues.jboss.org/browse/JBWS-3686 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3677) Save container registry in ServerConfigService.start() instead of install()

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3677?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3677: ---------------------------------- Fix Version/s: jbossws-cxf-4.2.1 (was: jbossws-cxf-4.3) > Save container registry in ServerConfigService.start() instead of install() > --------------------------------------------------------------------------- > > Key: JBWS-3677 > URL: https://issues.jboss.org/browse/JBWS-3677 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Affects Versions: jbossws-cxf-4.2 > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: jbossws-cxf-4.2.1 > > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3648) WS-Policy code-first improvements

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3648?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3648: --------------------------------------- Hi Joseph, I'll have a look and let you know, just need to finish some other things first. > WS-Policy code-first improvements > --------------------------------- > > Key: JBWS-3648 > URL: https://issues.jboss.org/browse/JBWS-3648 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, productivity > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > I'd like to see some kind of ws-policy oriented tooling in JBossWS. Ideally we should provide some mechanisms for basic code-first development; currently stuff like ws-security configuration through policies is actually contract based: the user is expected to either provide a wsdl with proper policies or to use policy attachment, which is basically the same, writing the actual policy assertion is required. > An idea could be to have a group of pre-defined policy assertions' sets for known scenarios (for ws-security those could be based e.g. on the Oasis WS-Security Policy Examples [1]). Each set would be composed of 'placement points' with a policy to be attached at each of those points. We'd then possibly have a custom CXF FactoryBeanListener to be registered in the FactoryBeanListenerManager; the new listener would perform something similar to what the PolicyAnnotationListener does (based on the @Policies/@Policy in the code), that is attaching policies to the proper attach points. An additional step would be to support merging (effective policy through Neethi?) multiple sets at the same time (say, you want e.g. a specific ws-security set plus a ws-rm set). > With such thing, we could provide the initial sets and let users pick the sets they want for a given endpoint (perhaps through a custom annotation, or possibly better specifying the sets' names within a property in a selected Endpoint Config). > The initial policy sets could be stored as xml files in one of the jbossws-cxf jars and we could provide a mechanism for reading additional ones from the current classpath (to let users add additional ones). > Finally, this would open up to further tooling improvements; e.g. 1) wsprovide could be enhanced to process the @EndpointConfig annotation, get the policy sets and produce a ws-policy enabled wsdl, 2) we could even provide an 'educational' gui tool showing assertions enabled/disabled depending on the selected sets, etc. > [1] http://docs.oasis-open.org/ws-sx/security-policy/examples/ws-sp-usecases-... -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3648) WS-Policy code-first improvements

by Joseph Hwang (JIRA)

[ https://issues.jboss.org/browse/JBWS-3648?page=com.atlassian.jira.plugin.... ] Joseph Hwang commented on JBWS-3648: ------------------------------------ Alessio, would you check this issues? https://community.jboss.org/thread/231657 Invoking @PolicySets-added Service Endpoint Interface is failed. I suggest to make another JIRA to solve this issues. I need your advice deperately > WS-Policy code-first improvements > --------------------------------- > > Key: JBWS-3648 > URL: https://issues.jboss.org/browse/JBWS-3648 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, productivity > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > I'd like to see some kind of ws-policy oriented tooling in JBossWS. Ideally we should provide some mechanisms for basic code-first development; currently stuff like ws-security configuration through policies is actually contract based: the user is expected to either provide a wsdl with proper policies or to use policy attachment, which is basically the same, writing the actual policy assertion is required. > An idea could be to have a group of pre-defined policy assertions' sets for known scenarios (for ws-security those could be based e.g. on the Oasis WS-Security Policy Examples [1]). Each set would be composed of 'placement points' with a policy to be attached at each of those points. We'd then possibly have a custom CXF FactoryBeanListener to be registered in the FactoryBeanListenerManager; the new listener would perform something similar to what the PolicyAnnotationListener does (based on the @Policies/@Policy in the code), that is attaching policies to the proper attach points. An additional step would be to support merging (effective policy through Neethi?) multiple sets at the same time (say, you want e.g. a specific ws-security set plus a ws-rm set). > With such thing, we could provide the initial sets and let users pick the sets they want for a given endpoint (perhaps through a custom annotation, or possibly better specifying the sets' names within a property in a selected Endpoint Config). > The initial policy sets could be stored as xml files in one of the jbossws-cxf jars and we could provide a mechanism for reading additional ones from the current classpath (to let users add additional ones). > Finally, this would open up to further tooling improvements; e.g. 1) wsprovide could be enhanced to process the @EndpointConfig annotation, get the policy sets and produce a ws-policy enabled wsdl, 2) we could even provide an 'educational' gui tool showing assertions enabled/disabled depending on the selected sets, etc. > [1] http://docs.oasis-open.org/ws-sx/security-policy/examples/ws-sp-usecases-... -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3685) JBossWS testsuite execution against WFLY w/ security manager enabled

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3685?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3685: ---------------------------------- Component/s: jbossws-cxf jbossws-integration productization > JBossWS testsuite execution against WFLY w/ security manager enabled > -------------------------------------------------------------------- > > Key: JBWS-3685 > URL: https://issues.jboss.org/browse/JBWS-3685 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration, productization > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2.1 > > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3685) JBossWS testsuite execution against WFLY w/ security manager enabled

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3685: ------------------------------------- Summary: JBossWS testsuite execution against WFLY w/ security manager enabled Key: JBWS-3685 URL: https://issues.jboss.org/browse/JBWS-3685 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.2.1 -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3684) AbstractServerConfig is not fully thread safe

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3684?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3684: ---------------------------------- Component/s: jbossws-integration > AbstractServerConfig is not fully thread safe > --------------------------------------------- > > Key: JBWS-3684 > URL: https://issues.jboss.org/browse/JBWS-3684 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2.1 > > > We have possible visibility issues with the webServiceHost, webServicePort, webServiceSecurePort, modifySOAPAddress members of the AbstractServerConfig. -- 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, 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 August 2013