-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
7.1.0.ER1
in the section Project Dependencies for Remote EJB Clients, there are two distinct, yet very similar ways how to add EJB client dependencis (the outcome of both is the same). Do we really need both? It looks somewhat confusing.
Option 1:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.jboss.bom</groupId>
<artifactId>jboss-eap-javaee7</artifactId>
<version>${version.jboss.bom.eap}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<!-- Include the EJB client JARs -->
<dependency>
<groupId>org.jboss.eap</groupId>
<artifactId>wildfly-ejb-client-bom</artifactId>
<type>pom</type>
<scope>compile</scope>
</dependency>
<!-- Include any additional dependencies required by the application
...
-->
</dependencies>
Option 2:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.jboss.eap</groupId>
<artifactId>wildfly-ejb-client-bom</artifactId>
<version>EJB_CLIENT_BOM_VERSION</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<dependency>
<groupId>org.jboss</groupId>
<artifactId>jboss-ejb-client</artifactId>
</dependency>
</dependencies>
I would vote for keeping just option 1, because it is included in the ejb-remote quickstart. Option 2 works too, but if we keep it (I don't mind if we keep both after all), the structure/wording of the chapter would need to be made more clear to imply that these are basically two different approaches to achieve the same dependency tree. Right now these two approaches seem too "separated" to me and the relationship between them is not obvious from the documentation.
- is incorporated by
-
JBEAP-20000 Modularize Developing Jakarta Enterprise Beans Applications
-
- Closed
-