Review the code which enable the mtom threshold configuration from DDEndpoint in both spring and without spring stack
----------------------------------------------------------------------------------------------------------------------
Key: JBWS-3166
URL: https://jira.jboss.org/browse/JBWS-3166
Project: JBoss Web Services
Issue Type: Task
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
We can probably add some more convenient APIs in cxf to configure the MTOMFeature easily.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/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
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
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
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
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
Alessio Soldano created JBWS-3529:
-------------------------------------
Summary: Enable configuration of properties
Key: JBWS-3529
URL: https://issues.jboss.org/browse/JBWS-3529
Project: JBoss Web Services
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: jbossws-cxf
Reporter: Alessio Soldano
Assignee: Alessio Soldano
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