[
https://issues.jboss.org/browse/WFLY-11144?page=com.atlassian.jira.plugin...
]
David Lloyd commented on WFLY-11144:
------------------------------------
Running {{jdeps}} seems to confirm that this is OK:
{noformat}
$ jdeps
~/.m2/repository/org/jboss/spec/javax/ejb/jboss-ejb-api_3.2_spec/1.0.1.Final/jboss-ejb-api_3.2_spec-1.0.1.Final.jar
jboss-ejb-api_3.2_spec-1.0.1.Final.jar -> java.base
jboss-ejb-api_3.2_spec-1.0.1.Final.jar -> java.naming
jboss-ejb-api_3.2_spec-1.0.1.Final.jar -> java.rmi
jboss-ejb-api_3.2_spec-1.0.1.Final.jar -> not found
javax.ejb -> java.io
java.base
javax.ejb -> java.lang
java.base
javax.ejb -> java.lang.annotation
java.base
javax.ejb -> java.rmi
java.rmi
javax.ejb -> java.security
java.base
javax.ejb -> java.util
java.base
javax.ejb -> java.util.concurrent
java.base
javax.ejb -> javax.transaction
not found
javax.ejb -> javax.xml.rpc.handler
not found
javax.ejb.embeddable -> java.io
java.base
javax.ejb.embeddable -> java.lang
java.base
javax.ejb.embeddable ->
java.net
java.base
javax.ejb.embeddable -> java.util
java.base
javax.ejb.embeddable -> java.util.regex
java.base
javax.ejb.embeddable -> javax.ejb
jboss-ejb-api_3.2_spec-1.0.1.Final.jar
javax.ejb.embeddable -> javax.ejb.spi
jboss-ejb-api_3.2_spec-1.0.1.Final.jar
javax.ejb.embeddable -> javax.naming
java.naming
javax.ejb.spi -> java.io
java.base
javax.ejb.spi -> java.lang
java.base
javax.ejb.spi -> java.util
java.base
javax.ejb.spi -> javax.ejb
jboss-ejb-api_3.2_spec-1.0.1.Final.jar
javax.ejb.spi -> javax.ejb.embeddable
jboss-ejb-api_3.2_spec-1.0.1.Final.jar
{noformat}
I don't see any dependencies that would have to come from {{javax.rmi.api}}.
Remove javax.ejb.api module dependency on javax.rmi.api
-------------------------------------------------------
Key: WFLY-11144
URL:
https://issues.jboss.org/browse/WFLY-11144
Project: WildFly
Issue Type: Task
Components: EJB
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Major
The javax.ejb.api module depends on javax.rmi.api. But I can't see any reason why;
the code in the spec jar does not import anything from any of the classes in the javax.rmi
and org.jboss.javax.rmi packages that the javax.rmi.api module exports.
This is important because javax.rmi.api brings in a huge dependency tree. That module is
really just a wrapper around javax.orb.api, exporting a subset of its packages. And
javax.orb.api is a misnomer -- it's not just API, it's the entire orb, with
implementation dependencies that transitively bring in a large chunk of the entire
appserver codebase.
So if javax.ejb.api does not need javax.rmi.api we need to remove that link.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)