Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-2603

EJB3 update

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Blocker
    • JBossAS-4.0.4RC1
    • None
    • EJB2
    • None

    Description

      The ejb3 codebase and dependencies need to be updated for the 4.0.4RC1 release.

      Attachments

        Issue Links

          is blocked by

          Feature Request - Feature requests from customers and/or users EJBTHREE-394 Output better exceptions when failing to bind into JNDI

          • 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

          Bug - A problem that impairs or prevents the functions of the product. EJBTHREE-380 EJB3 swallows runtime exception stack traces

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBAS-2606 Default JBoss+EJB3 boostrap very slow due to TreeCache

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

          Bug - A problem that impairs or prevents the functions of the product. EJBTHREE-232 After some time: Exception in thread "Timer-5" java.lang.NoClassDefFoundError: javax/xml/rpc/handler/MessageContext

          • 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

          Bug - A problem that impairs or prevents the functions of the product. EJBTHREE-270 Redeployment of stateful bean fails

          • 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

          Task - Represents a small unit of work that is not end-user facing. EJBTHREE-360 UserTransaction needs to be bound in embeddable

          • 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

          Task - Represents a small unit of work that is not end-user facing. JBAS-2604 Update the remoting version to a stable release

          • 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

          Activity

            People

              patriot1burke@gmail.com Bill Burke (Inactive)
              starksm64 Scott Stark (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: