Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 7.0.1.Final
    • Fix Version/s: 7.1.0.Final
    • Component/s: Clustering
    • Labels:
      None

      Description

      IF a binder service is registered as ON_DEMAND then the item will not be available for lookup in JNDI until something as expressed a dependency on it. This means that it will work for resource injection, however will fail for manual JNDI lookups.

      If lazy startup is required the binder service should use a ManagedReferenceFactory that starts the lazy service and blocks until the lazy service is available.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  pferraro Paul Ferraro
                  Reporter:
                  swd847 Stuart Douglas
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  7 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: