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

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Out of Date
    • Affects Version/s: None
    • Fix Version/s: No Release
    • Component/s: Naming
    • Labels:
      None
    • Affects:
      Documentation (Ref Guide, User Guide, etc.), Release Notes, Compatibility/Configuration

      Description

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  brian.stansberry Brian Stansberry
                  Reporter:
                  brian.stansberry Brian Stansberry
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: