jbossws-issues October 2013

jbossws-issues@lists.jboss.org

1 participants
65 discussions

[JBoss JIRA] (JBWS-3713) Allow better control over Apache CXF bus creation for JAXWS clients

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3713: ------------------------------------- Summary: Allow better control over Apache CXF bus creation for JAXWS clients Key: JBWS-3713 URL: https://issues.jboss.org/browse/JBWS-3713 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Assignee: 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3378) JSR 109 - explicit JAXWS handler authorization for EJB3 endpoints

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3378?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3378: ---------------------------------- Description: JSR 109 - Version 1.3 - Chapter 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. was: JSR 109 - Version 1.3 - Chapter 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. JSR 109 - Version 1.3 - Chapter 6.2.2.5 Transactions Handlers run under the transaction context of the component they are associated with. > JSR 109 - explicit JAXWS handler authorization for EJB3 endpoints > ----------------------------------------------------------------- > > Key: JBWS-3378 > URL: https://issues.jboss.org/browse/JBWS-3378 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Richard Opalka > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > JSR 109 - Version 1.3 - Chapter 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 For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3378) JSR 109 - explicit JAXWS handler authorization for EJB3 endpoints

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3378?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3378: ---------------------------------- Summary: JSR 109 - explicit JAXWS handler authorization for EJB3 endpoints (was: JAXWS handlers (like JAXRPC handlers are) have to be executed in EJB component interceptor) > JSR 109 - explicit JAXWS handler authorization for EJB3 endpoints > ----------------------------------------------------------------- > > Key: JBWS-3378 > URL: https://issues.jboss.org/browse/JBWS-3378 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Richard Opalka > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > JSR 109 - Version 1.3 - Chapter 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. > JSR 109 - Version 1.3 - Chapter 6.2.2.5 Transactions > Handlers run under the transaction context of the component they are associated with. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3712) Wrong processing of compressed zero (::) format IPv6 addresses

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3712?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3712: ---------------------------------- Description: The changes for JBWS-3652 seem to have introduced a bug with IPv6 addresses containing "::". The AbstractServerConfig#toIPv6URLFormat(String host) method erroneously treats those addresses as non-IPv6 literal IP addresses, hence they're not wrapped in square brackets. This later leads to endpoints not being usable if the AS wsdl-host is set to such compressed zero IPv6 addresses. was: The changes for JBWS-3652 seems to have introduced a bug with IPv6 addresses containing "::". The AbstractServerConfig#toIPv6URLFormat(String host) method erroneously treats those addresses as non-IPv6 literal IP addresses, hence they're not wrapped in square brackets. This later leads to endpoints not being usable if the AS wsdl-host is set to such compressed zero IPv6 addresses. > Wrong processing of compressed zero (::) format IPv6 addresses > -------------------------------------------------------------- > > Key: JBWS-3712 > URL: https://issues.jboss.org/browse/JBWS-3712 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Affects Versions: jbossws-cxf-4.2.1 > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > The changes for JBWS-3652 seem to have introduced a bug with IPv6 addresses containing "::". The AbstractServerConfig#toIPv6URLFormat(String host) method erroneously treats those addresses as non-IPv6 literal IP addresses, hence they're not wrapped in square brackets. > This later leads to endpoints not being usable if the AS wsdl-host is set to such compressed zero IPv6 addresses. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3712) Wrong processing of compressed zero (::) format IPv6 addresses

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3712: ------------------------------------- Summary: Wrong processing of compressed zero (::) format IPv6 addresses Key: JBWS-3712 URL: https://issues.jboss.org/browse/JBWS-3712 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Affects Versions: jbossws-cxf-4.2.1 Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.3 The changes for JBWS-3652 seems to have introduced a bug with IPv6 addresses containing "::". The AbstractServerConfig#toIPv6URLFormat(String host) method erroneously treats those addresses as non-IPv6 literal IP addresses, hence they're not wrapped in square brackets. This later leads to endpoints not being usable if the AS wsdl-host is set to such compressed zero IPv6 addresses. -- 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, 6 months

1
0
0 / 0

← Newer
1
2
3
4
5
6
7
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues October 2013