-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
We currently expect users deploying a WS-Trust STS endpoint to set a dependency to org.apache.cxf.impl module, to gain visibility on the org.apache.cxf.ws.security.sts.provider.SecurityTokenServiceProvider class as well as misc utility classes from cxf-services-sts-core.jar.
This has the side effect of exposing impl details of the whole Apache CXF to the deployment, as well as generating a warning in the logs as that module is private.
Moreover, should JAX-RS annotations be added to any of the jars we have in the cxf module, the STS deployment would fail due to the way jaxrs subsystem works on WildFly.
We should hence set a dependency to an independent module which should filter the exported classes (at least we should only expose the contents of the cxf-services-sts-core and cxf-rt-ws-security jars).
- is cloned by
-
-
- Closed
-
- is related to
-
WFCORE-1372 CompositeIndexProcessor::calculateModuleIndex does not respect import filters
-
- Open
-
- relates to
-
JBWS-3982 Clean-up test deployment dependencies
-
- Closed
-
-
-
- Closed
-
