[
https://issues.jboss.org/browse/JBWS-3329?page=com.atlassian.jira.plugin....
]
Alessio Soldano updated JBWS-3329:
----------------------------------
Summary: Implement protocol binding filtering for handlers coming from endpoint
configuration (was: Implement handlers protocol binding filtering)
Description:
When adding handlers declared through the default endpoint configs, we currently ignore
protocol binding filtering.
That's a potential issue as the Apache CXF HTTPBinding implementation verifies the
kind of handler (Logical or Protocol) that are added to the endpoint. So erroneously
adding a SOAP handler to a HTTPBinding endpoint blows up the deployment.
was:
When adding handlers (for instance declared through the default endpoint configs), we
currently ignore protocol binding filtering.
That's a potential issue as the Apache CXF HTTPBinding implementation verifies the
kind of handler (Logical or Protocol) that are added to the endpoint. So erroneously
adding a SOAP handler to a HTTPBinding endpoint blows up the deployment.
Implement protocol binding filtering for handlers coming from
endpoint configuration
------------------------------------------------------------------------------------
Key: JBWS-3329
URL:
https://issues.jboss.org/browse/JBWS-3329
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.0
When adding handlers declared through the default endpoint configs, we currently ignore
protocol binding filtering.
That's a potential issue as the Apache CXF HTTPBinding implementation verifies the
kind of handler (Logical or Protocol) that are added to the endpoint. So erroneously
adding a SOAP handler to a HTTPBinding endpoint blows up the deployment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira