June 2012 - jbossws-issues - Jboss List Archives

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

by Jim Ma (JIRA)

SpringBusHolder.createBus(URL location) does not support the bean class annotated with @PostConstruct ------------------------------------------------------------------------------------------------------ Key: JBWS-3172 URL: https://jira.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 Fix For: jbossws-cxf-4.0 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. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
2
0 / 0

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

by Alessio Soldano (JIRA)

12 years, 2 months

1
1
0 / 0

[JBoss JIRA] (JBWS-3510) Add WSProvide option for specifying soap:address location to use in generated wsdl

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3510: ------------------------------------- Summary: Add WSProvide option for specifying soap:address location to use in generated wsdl Key: JBWS-3510 URL: https://issues.jboss.org/browse/JBWS-3510 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, tools-jaxws Reporter: Alessio Soldano Fix For: jbossws-cxf-4.1 Expose an option for specifying soap:address location to use in generated wsdl. Basically the same Apache CXF Java2WS does with -a / -address. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBWS-2710) Provide testcase for WS-Trust (server side) and WS-SecureConversation

by Alessio Soldano (JIRA)

Provide testcase for WS-Trust (server side) and WS-SecureConversation --------------------------------------------------------------------- Key: JBWS-2710 URL: https://jira.jboss.org/jira/browse/JBWS-2710 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano http://cwiki.apache.org/CXF20DOC/ws-trust.html http://cwiki.apache.org/CXF20DOC/ws-secureconversation.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
4
0 / 0

[JBoss JIRA] (JBWS-3504) Add ability to configure the CXF policy alternative selector on server side

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3504: ------------------------------------- Summary: Add ability to configure the CXF policy alternative selector on server side Key: JBWS-3504 URL: https://issues.jboss.org/browse/JBWS-3504 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.1 As a consequence of JBWS-3149, JBossWS-CXF defaults to MaximalAlternativeSelector on server side. We need an option for letting users configure a different behavior if they really want to. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
2
0 / 0

[JBoss JIRA] (JBWS-3378) Both JAXWS & JAXRPC handlers have to be executed in EJB interceptor after EJB security interceptors

by Richard Opalka (Created) (JIRA)

Both JAXWS & JAXRPC handlers have to be executed in EJB interceptor after EJB security interceptors --------------------------------------------------------------------------------------------------- Key: JBWS-3378 URL: https://issues.jboss.org/browse/JBWS-3378 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Richard Opalka 6.2.2.4 Security Handlers associated with a Port component run after authorization has occurred and before the business logic method of the Service Implementation bean is dispatched to. For JAX-RPC or JAX-WS Service endpoints, Handlers run after the container has performed the security constraint checks associated with the servlet element that defines the Port component. For EJB based service implementations, Handlers run after method level authorization has occurred. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

7
11
0 / 0

[JBoss JIRA] Created: (JBWS-3237) Set an HTTP proxy host/port for an individual WS-stub

by Roger Hui (JIRA)

Set an HTTP proxy host/port for an individual WS-stub ----------------------------------------------------- Key: JBWS-3237 URL: https://issues.jboss.org/browse/JBWS-3237 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.4.1 Environment: EAP 4.3.X and EAP 5.x Reporter: Roger Hui Priority: Minor We would like to set an HTTP proxy host/port for an individual WS-stub. We found [1], but the link goes to a dead page [2], and we found a valid JBoss Remoting page [3]. In [3] it shows that the proxy host/port can be configured in the client metadata. However, we don't see how to set this from JBossWS. We would like this to be a new feature. [1] http://community.jboss.org/wiki/JBossWS-FAQ#How_can_I_setup_my_client_to_... [2] http://labs.jboss.com/jbossremoting/docs/guide/ch05.html [3] http://docs.jboss.org/jbossremoting/docs/guide/2.5/html/index.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
6
0 / 0

[JBoss JIRA] (JBWS-3496) Enable CXF WS-MetadataExchange (Aug 2006 spec) support

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3496: ------------------------------------- Summary: Enable CXF WS-MetadataExchange (Aug 2006 spec) support Key: JBWS-3496 URL: https://issues.jboss.org/browse/JBWS-3496 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.1 Apache CXF 2.5.x comes with WS-MetadataExchange ( http://schemas.xmlsoap.org/ws/2004/09/mex/ ) support. While we're probably going to explore supporting the newer version included in the WS-RA specs, we should start by unlocking the implementation already available from Apache CXF. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
1
0 / 0

[JBoss JIRA] (JBWS-3500) @SchemaValidation doesn't work in JBoss 7.1.1 Final

by Jim Ma (JIRA)

Jim Ma created JBWS-3500: ---------------------------- Summary: @SchemaValidation doesn't work in JBoss 7.1.1 Final Key: JBWS-3500 URL: https://issues.jboss.org/browse/JBWS-3500 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

4
8
0 / 0

[JBoss JIRA] Created: (JBWS-2932) Support for HTTP Digest authentication, when acting as a client to an external web service

by Ian (JIRA)

Support for HTTP Digest authentication, when acting as a client to an external web service ------------------------------------------------------------------------------------------ Key: JBWS-2932 URL: https://jira.jboss.org/jira/browse/JBWS-2932 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-metro-3.2.1, jbossws-native-3.2.1, jbossws-cxf-3.2.1 Reporter: Ian Please implement HTTP Digest Authentication when acting as a client to an external web service. I don't mean using WS-Security, just using HTTP authentication in a similar that Basic Authentication is used - using JAX-WS code similar to this: String url = configuration.getString(CONFIG_URL); BindingProvider provider = (BindingProvider)requestInvoker; provider.getRequestContext().put(BindingProvider.USERNAME_PROPERTY, username); provider.getRequestContext().put(BindingProvider.PASSWORD_PROPERTY, password); This code works if run as a standalone java client (probably because Metro supports it). However it doesn't work with JBossWS: * Native implementation simply doesn't work at all * Metro implementation has classloading issues when web service calls are made (to do with WS-Addressing I think, I've seen other posts about it). * CXF has the same issues as Metro Given from my reading that the WS-Security work supports Digest authentication, it doesn't seem a difficult task. I'd suggest one of two ways to fix it: 1. Implement it in JBossWS native, OR 2. Fix the classloading issues in Metro and/or CXF so those stacks can be used (given they already support it). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues June 2012