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

Move RemoteNamingBean to deploy

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Obsolete
    • Icon: Major Major
    • No Release
    • None
    • Naming
    • None
    • Documentation (Ref Guide, User Guide, etc.), Release Notes, Compatibility/Configuration

      RemoteNamingBean is currently in deployers. Move it to deploy. Bean Validation's JndiBinder is using JNDI in deployers, but it only needs LocalNamingBean. Once LocalNamingBean is deployed, any new InitialContext() call inside the AS will find the local server, so that should be sufficient; nothing in deployers should need RemoteNamingBean.

          1.
          		 Restore NamingProviderUrlWriter Sub-task Closed Critical Brian Stansberry

              bstansbe@redhat.com Brian Stansberry
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: