May 2013 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3172) SpringBusHolder.createBus(URL location) does not support the bean class annotated with @PostConstruct

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3172?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3172: ---------------------------------- Fix Version/s: (was: jbossws-cxf-4.2) > SpringBusHolder.createBus(URL location) does not support the bean class annotated with @PostConstruct > ------------------------------------------------------------------------------------------------------ > > Key: JBWS-3172 > URL: https://issues.jboss.org/browse/JBWS-3172 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-native-3.4.0.CR1 > Reporter: Jim Ma > Assignee: Jim Ma > Priority: Optional > > SpringBusHolder has the same issue with https://issues.apache.org/jira/browse/CXF-3157. > Look at if load the jbossws-cxf.xml with FileSystemXmlApplicationContext can fix this issue. -- 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, 11 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.3 (was: jbossws-cxf-4.2) > 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.3 > > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3586) Message log browser functionality

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3586?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3586: ---------------------------------- Fix Version/s: jbossws-cxf-4.3 (was: jbossws-cxf-4.2) > Message log browser functionality > --------------------------------- > > Key: JBWS-3586 > URL: https://issues.jboss.org/browse/JBWS-3586 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration, productivity > Reporter: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > I'd like to see a SOAP message log browsing functionality for JBossWS / JBoss AS. This should basically be something like the Apache CXF LogBrowser [1] yet integrated with the AS management / console. > We should also evaluate whether it's possible to convert CXF generated logs into the JBossWS SPI Records [4] (in any case, any AS level handling of cxf stuff needs to be hidden behind JBossWS SPI). > Finally we might explore additional functionalities / uses of logs which could be implemented; see for instance [2] and [3]. > [1] http://cxf.apache.org/docs/logbrowser-configuration.html > [2] http://cxf.apache.org/docs/debugging-and-logging.html#DebuggingandLogging... > [3] http://sberyozkin.blogspot.it/2012/07/cxf-log-browser-demo.html > [4] https://community.jboss.org/wiki/JBossWS-RecordsManagement -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3514) HTTP session scope support

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3514?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3514: ---------------------------------- Fix Version/s: jbossws-cxf-4.3 (was: jbossws-cxf-4.2) > HTTP session scope support > -------------------------- > > Key: JBWS-3514 > URL: https://issues.jboss.org/browse/JBWS-3514 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > Solerman Kaplon says: > "Hello everyone, after metro stack got discontinued and CXF becoming the de-facto stack for JbossWS, I'm missing the @HttpSessionScope annotation. Basically, it automatically adds the jsession id to every http response so sessions can be tracked as usual in HTTP. For instance, that allows one to carry CDI/Seam conversations over several WS requests, very useful for rich clients. I would like for something to be included by default in jboss ws to allow for the same level of usability. Right now, the only alternative is to manually fiddle with the webservice context and add the header yourself. Another level of automation would be a Message Handler of Interceptor to do the job. Any other ideas?" > See also: > http://weblogs.java.net/blog/kohsuke/archive/2006/10/bringing_state.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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3610) Review of AccessController and PrivilegedAction use across JBossWS

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3610?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3610: ---------------------------------- Issue Type: Task (was: Feature Request) > Review of AccessController and PrivilegedAction use across JBossWS > ------------------------------------------------------------------ > > Key: JBWS-3610 > URL: https://issues.jboss.org/browse/JBWS-3610 > 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 > > > See https://issues.jboss.org/browse/AS7-6316 description; most of that (especially on use of singletons for no param privileged actions) needs to be done on JBossWS codebase too. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3638) Fix SecurityDomainTestCase failure only happens with IBM JDK6

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/JBWS-3638?page=com.atlassian.jira.plugin.... ] Jim Ma updated JBWS-3638: ------------------------- Summary: Fix SecurityDomainTestCase failure only happens with IBM JDK6 (was: Fiix SecurityDomainTestCase failure only happens with IBM JDK6) > Fix SecurityDomainTestCase failure only happens with IBM JDK6 > ------------------------------------------------------------- > > Key: JBWS-3638 > URL: https://issues.jboss.org/browse/JBWS-3638 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.1.3 > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: jbossws-cxf-4.2 > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3640) Failed to get jmx connection in JBWS2150TestCaseForked on Windows

by Jim Ma (JIRA)

Jim Ma created JBWS-3640: ---------------------------- Summary: Failed to get jmx connection in JBWS2150TestCaseForked on Windows Key: JBWS-3640 URL: https://issues.jboss.org/browse/JBWS-3640 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-4.1.3 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.2 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3639) Add more timeout value for the thread join to fix the JBWS1666TestCase failure on Windows

by Jim Ma (JIRA)

Jim Ma created JBWS-3639: ---------------------------- Summary: Add more timeout value for the thread join to fix the JBWS1666TestCase failure on Windows Key: JBWS-3639 URL: https://issues.jboss.org/browse/JBWS-3639 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-4.1.3 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.2 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3638) Fiix SecurityDomainTestCase failure only happens with IBM JDK6

by Jim Ma (JIRA)

Jim Ma created JBWS-3638: ---------------------------- Summary: Fiix SecurityDomainTestCase failure only happens with IBM JDK6 Key: JBWS-3638 URL: https://issues.jboss.org/browse/JBWS-3638 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-4.1.3 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.2 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3637) Fix JBWS1702TestCase failure with IBM JDK7

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/JBWS-3637?page=com.atlassian.jira.plugin.... ] Jim Ma updated JBWS-3637: ------------------------- Summary: Fix JBWS1702TestCase failure with IBM JDK7 (was: Fix JBWS1702TestCase failure with IBM JDK6 ) > Fix JBWS1702TestCase failure with IBM JDK7 > ------------------------------------------ > > Key: JBWS-3637 > URL: https://issues.jboss.org/browse/JBWS-3637 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.1.3 > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: jbossws-cxf-4.2 > > -- 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, 11 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 May 2013