[jboss-jira] [JBoss JIRA] (WFLY-5967) Have web services add javax.xml.rpic.api dependency to deployments instead of EjbDependencyDeploymentUnitProcessor

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-5967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated WFLY-5967:
-----------------------------------
    Component/s: EJB


> 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: Alessio Soldano
>
> 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
(v6.4.11#64026)