[jboss-jira] [JBoss JIRA] (WFLY-5967) Have web services add javax.xml.rpic.api dependency to deployments instead of EjbDependencyDeploymentUnitProcessor
Alessio Soldano (Jira)
issues at jboss.org
Tue Nov 26 09:13:03 EST 2019
[ https://issues.jboss.org/browse/WFLY-5967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alessio Soldano reassigned WFLY-5967:
-------------------------------------
Assignee: Jim Ma (was: Alessio Soldano)
> Have web services add javax.xml.rpic.api dependency to deployments instead of EjbDependencyDeploymentUnitProcessor
> -------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-5967
> URL: https://issues.jboss.org/browse/WFLY-5967
> Project: WildFly
> Issue Type: Task
> Components: EJB, Web Services
> Affects Versions: 10.0.0.CR5
> Reporter: Brian Stansberry
> Assignee: Jim Ma
> Priority: Major
>
> Prior to WFLY-5922, the packages in the javax.xml.rpic.api module were being made available to deployments because EjbDependencyDeploymentUnitProcessor added the javax.ejb.api module, and javax.ejb.api *exported* javax.xml.rpc.api.
> WFLY-5922 removed that export, which broke the TCK signature tests. So I'm about to put up a workaround PR that has EjbDependencyDeploymentUnitProcessor directly add a dep on javax.xml.rpc.api.
> That's a workaround for 10.0.0.Final, but Jason noted he thought it would make more sense for this dep to come from the ws subsystem. So this JIRA is to track looking into that.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
More information about the jboss-jira
mailing list