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

Binder services should not be ON_DEMAND

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • 7.1.0.Final
    • 7.0.1.Final
    • Clustering
    • None

      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.

              pferraro@redhat.com Paul Ferraro
              sdouglas1@redhat.com Stuart Douglas (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: