[
https://issues.jboss.org/browse/WFLY-3535?page=com.atlassian.jira.plugin....
]
Alessio Soldano commented on WFLY-3535:
---------------------------------------
Frankly speaking, I prefer not to do this. Forgetting to add cxf module dependency is as
easy as forgetting any other module dependency.
The reason why cxf dependency is not added by default is because cxf module is a big one
(it's not the annotations only) and we want to encourage users to write applications
as portable as possible. Basically I prefer first time users to think about what
they're doing, look at the possible solutions and eventually decide they need CXF and
hence add the dependency (the same they'd do with other deps).
To me, the fact the annotations from missing dependencies are silently ignored is a
different problem, which I originally raised years ago but looks like that's not
something being worked.
Implicitly add org.apache.cxf module to deployments with JAX-WS
endpoints
-------------------------------------------------------------------------
Key: WFLY-3535
URL:
https://issues.jboss.org/browse/WFLY-3535
Project: WildFly
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 8.0.0.Final
Reporter: Kyle Lape
Assignee: Alessio Soldano
This seems like a particularly easy module to forget to add as a dependency in a
deployment, and can be difficult to figure out if you're adding a CXF annotation and
it inexplicably doesn't work.
The module is public, so this should be relatively low-risk to add.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)