Uploaded image for project: 'EJB 3.0'
  1. EJB 3.0
  2. EJBTHREE-1127

Rework implementation requirements for @Remote, @RemoteHome

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Critical
    • AS 5.0.0.Beta3
    • None
    • None
    • None

    Description

      @RemoteHome is sufficient for a 2.1 view; the Remote Interface can be inferred from the return type of the create method.

      @Remote specifying a 2.1 Interface requires a @RemoteHome.

      @Remote specifying a Business Interface does not require a home; results in remote 3.0 view.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBAS-5036 Local home create() implementation returns wrong type

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. EJBTHREE-1155 Allow for discovery of N Local/Remote interfaces through Home create<METHOD>() methods

          • 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.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. EJBTHREE-1156 Ensure Stateless EJBs 2.1 Home define only one "create()" method with no arguments

          • 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.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. EJBTHREE-1075 Ensure Session Beans with Incomplete 2.1 View Fail Deployment

          • 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.
          • Closed

          Activity

            People

              arubinge@redhat.com Andrew Rubinger (Inactive)
              arubinge@redhat.com Andrew Rubinger (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: