EasyBeans
  1. EasyBeans
  2. EZB-165

A client can not access to different remote JNDI contexts

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: EasyBeans 1.0 M6
    • Fix Version/s: EasyBeans 1.0 RC1
    • Component/s: SmartClient
    • Labels:
      None
    • Global Rank:
      2536

      Description

      The class org.objectweb.easybeans.component.smartclient.spi.SmartContextFactory do not consider many different servers. For performance reasons, a classloader is attached to the factory to avoid classes downloads on each EJB3 call. A consequence is that the parameter Context.PROVIDER_URL specified on each javax.naming.InitialContext is saved statically, so a client can access to only one JNDI context (the first used).

      In the following example, ctx2 requests the url1 instead of the url2 :

      Hashtable h1 = new Hashtable();

      put(Context.PROVIDER_URL, url1);

      put(Context.INITIAL_CONTEXT_FACTORY , "org.objectweb.easybeans.component.smartclient.spi.SmartContextFactory");

      Context ctx1 = new InitialContext(h1);

      Hashtable h2 = new Hashtable();

      put(Context.PROVIDER_URL, url2);

      put(Context.INITIAL_CONTEXT_FACTORY , "org.objectweb.easybeans.component.smartclient.spi.SmartContextFactory");

      Context ctx2 = new InitialContext(h2);

        Activity

        Hide
        Florent Benoit
        added a comment -

        Was fixed 3 weeks ago but forgot to close the issue

        Show
        Florent Benoit
        added a comment - Was fixed 3 weeks ago but forgot to close the issue
        Hide
        Loïc Albertin
        added a comment -

        Closing old resolved issues

        Show
        Loïc Albertin
        added a comment - Closing old resolved issues

          People

          • Assignee:
            Florent Benoit
            Reporter:
            Simon Brandhof
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Issue deployment