Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-10877

Backport EAP7-325 to legacy EJB client

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Obsolete
    • Critical
    • None
    • 7.1.0.DR18
    • EJB, User Experience
    • None
    • 0
    • 0% 0%

    Description

      Something akin to EAP7-325 should be applied to the legacy EJB client (3.0.x) as well.

      With EJB client 4.x, when using EAP BOM to manage versions, I can have a short dependencies section in pom.xml like this:

      <dependency>
                    <groupId>org.jboss</groupId>
                    <artifactId>jboss-ejb-client</artifactId>
</dependency>

      With the legacy client (currently 3.0.0.Beta7), I have to do this

                <dependency>
                    <groupId>org.jboss</groupId>
                    <artifactId>jboss-ejb-client-legacy</artifactId>
                </dependency>
                <dependency>
                    <groupId>org.jboss.xnio</groupId>
                    <artifactId>xnio-api</artifactId>
                </dependency>
                <dependency>
                    <groupId>org.jboss.xnio</groupId>
                    <artifactId>xnio-nio</artifactId>
                </dependency>
                <dependency>
                    <groupId>org.jboss.ejb3</groupId>
                    <artifactId>jboss-ejb3-ext-api</artifactId>
                </dependency>
                <dependency>
                    <groupId>org.jboss.spec.javax.transaction</groupId>
                    <artifactId>jboss-transaction-api_1.2_spec</artifactId>
                </dependency>
                <dependency>
                    <groupId>org.jboss.spec.javax.ejb</groupId>
                    <artifactId>jboss-ejb-api_3.2_spec</artifactId>
                </dependency>
                <dependency>
                    <groupId>org.jboss.marshalling</groupId>
                    <artifactId>jboss-marshalling-river</artifactId>
                </dependency>

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users JBEAP-10897 Documentation about the legacy EJB client

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users JBEAP-10759 Add bom for legacy compatibility library, and tests to verify usage

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              rhn-support-tmiyargi Teresa Miyar Gil (Inactive)
              jmartisk@redhat.com Jan Martiska
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: