Uploaded image for project: 'WildFly EJB HTTP Client'
  1. WildFly EJB HTTP Client
  2. WEJBHTTP-69

Iterate over jndi names not possible with http based access

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 1.1.11.Final
    • 1.1.9.Final
    • None
    • Hide

       

      final Hashtable<String, String> jndiProperties = new Hashtable<>();
jndiProperties.put(Context.INITIAL_CONTEXT_FACTORY, "org.wildfly.naming.client.WildFlyInitialContextFactory");
jndiProperties.put(Context.PROVIDER_URL, "http://localhost:8080/wildfly-services");
final Context context = new InitialContext(jndiProperties);
final NamingEnumeration<NameClassPair> tList = context.list("/");

       

      Show
        final Hashtable< String , String > jndiProperties = new Hashtable<>(); jndiProperties.put(Context.INITIAL_CONTEXT_FACTORY, "org.wildfly.naming.client.WildFlyInitialContextFactory" ); jndiProperties.put(Context.PROVIDER_URL, "http: //localhost:8080/wildfly-services" ); final Context context = new InitialContext(jndiProperties); final NamingEnumeration<NameClassPair> tList = context.list( "/" );  

    Description

      when using remote JNDI over HTTP it is not possible to iterate through JNDI Names with context.list -> java.io.NotSerializableException: org.jboss.as.naming.util.NamingUtils$1

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-15511 Iterate over jndi names not possible with http based access

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-16215 Upgrade wildfly-http-ejb-client from 1.1.10.Final to 1.1.11.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              istudens@redhat.com Ivo Studensky
              istudens@redhat.com Ivo Studensky
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: