[
https://issues.jboss.org/browse/JBWS-3884?page=com.atlassian.jira.plugin....
]
Alessio Soldano updated JBWS-3884:
----------------------------------
Description:
The JBossWS integration with Spring has been evolving a lot since the initial prototype in
3.x series. WIth the latest additions in JBossWS 5 (see linked jiras), it's now time
to deprecate the Spring integration, that is the ability of declaring ws endpoints and
clients using spring based descriptors. This has proven to be a difficult to maintain
solution and with the current stack functionalities there's really no reason for
relying on it. We do have valid alternatives for configuring interceptors, features,
setting WS-* options, controlling CXF internals, performing injection into EE components,
etc.
In any case, the Spring integration has been disabled by default (optionally turned on by
manually installing spring module on the container) since JBoss AS 7 series and users
should now be properly relying on plain JAX-WS whenever possible and using WS-Policy and
JBossWS configuration properties for advanced WS-* functionalities, so this is not going
to be that an issue to the majority of the user base.
was:
The JBossWS integration with Spring has been evolving a lot since the initial prototype in
3.x series. WIth the latest additions in JBossWS 5 (see linked jiras), it's now time
to deprecate the Spring integration, that is the ability of declaring ws endpoints and
clients using spring based descriptors. This has proven to be a difficult to maintain
solution and with the current stack functionalities there's really no reason for
relying on it. We do have valid alternatives for configuring interceptors, features,
setting WS-* options, controlling CXF internals, performing injection into EE components,
etc.
In any case, the Spring integration has been disabled by default (optionally turned on by
manually installing spring module on the container) since JBoss AS 7 series and users
should now be properly relying on plain JAX-WS whenever possible and using WS-Policy and
JBossWS configuration properties for advanced WS-* functionalities.
Deprecate Spring integration
----------------------------
Key: JBWS-3884
URL:
https://issues.jboss.org/browse/JBWS-3884
Project: JBoss Web Services
Issue Type: Task
Components: jbossws-cxf, jbossws-integration
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: jbossws-cxf-5.0
The JBossWS integration with Spring has been evolving a lot since the initial prototype
in 3.x series. WIth the latest additions in JBossWS 5 (see linked jiras), it's now
time to deprecate the Spring integration, that is the ability of declaring ws endpoints
and clients using spring based descriptors. This has proven to be a difficult to maintain
solution and with the current stack functionalities there's really no reason for
relying on it. We do have valid alternatives for configuring interceptors, features,
setting WS-* options, controlling CXF internals, performing injection into EE components,
etc.
In any case, the Spring integration has been disabled by default (optionally turned on by
manually installing spring module on the container) since JBoss AS 7 series and users
should now be properly relying on plain JAX-WS whenever possible and using WS-Policy and
JBossWS configuration properties for advanced WS-* functionalities, so this is not going
to be that an issue to the majority of the user base.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)