Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-1338

Remote JNDI support for AS7

    XMLWordPrintable

Details

    Description

      Add support for remote JNDI after all. It was agreed that:

      • Remote JNDI would run over Remoting
      • Remote JNDI for EJB is strictly a legacy access protocol, deprecated in favor of "ejb:"
      • The Remote JNDI service would proxy to a specific Context of the server JNDI tree - maybe "java:jboss/shared", maybe something else
      • Server-side services would opt-in to Remote JNDI; initially we'd only support:
        • Remote EJB interfaces
        • HornetQ connection factories
      • In the future we may support:
        • User bindings, so long as they're serializable
      • In the future we will never support:
        • Proxied DataSources
        • Proxied JMS invocations

      Initial project tree is at https://github.com/dmlloyd/jboss-remote-jndi for now.

      Attachments

        Issue Links

          is duplicated by

          Feature Request - Feature requests from customers and/or users AS7-3437 JMS clients - Remote JNDI lookup does not work in EAP6/AS7

          • 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
          is related to

          Feature Request - Feature requests from customers and/or users AS7-3437 JMS clients - Remote JNDI lookup does not work in EAP6/AS7

          • 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. AS7-423 Remote EJB (non-IIOP)

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

          Task - Represents a small unit of work that is not end-user facing. AS7-1709 Client JNDI support for AS7

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

          Task - Represents a small unit of work that is not end-user facing. JBWS-3454 Additional tests for SOAP-over-JMS and AS7 remote connection factory

          • 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

              johnbailey_jira John Bailey (Inactive)
              ropalka Richard Opalka
              Votes:
              18 Vote for this issue
              Watchers:
              43 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: