Bug 1477945 - The environment and cache fields are not shown on the JBoss ON page when viewing the configuration of /subsystem=naming/binding entries
The environment and cache fields are not shown on the JBoss ON page when view...
Product: JBoss Operations Network
Classification: JBoss
Component: Plugin -- JBoss EAP 6 (Show other bugs)
JON 3.3.8
Unspecified Unspecified
high Severity high
: CR01
: One-off release
Assigned To: Ruben Vargas Palma
Filip Brychta
: Triaged
Depends On: 1477947
Blocks: 1387292
  Show dependency treegraph
Reported: 2017-08-03 05:47 EDT by bkramer
Modified: 2018-02-16 05:02 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1478094 (view as bug list)
Last Closed: 2018-02-16 05:02:18 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3136541 None None None 2017-08-03 05:48 EDT

  None (edit)
Description bkramer 2017-08-03 05:47:23 EDT
Description of problem:
The environment and cache fields are not shown on the JBoss ON page when viewing the configuration of /subsystem=naming/binding entries

Version-Release number of selected component (if applicable):
JBoss ON 3.3.8

How reproducible:
Every time

Steps to Reproduce:
1. Add object-factory JNDI to the EAP 6 and EAP 7. For instance something like this is added in the standalone.xml file:

<subsystem xmlns="urn:jboss:domain:naming:2.0">
      <object-factory name="java:global/MongoClient" module="com.mongodb.jndi" class="com.mongodb.jndi.MongoClientJNDIFactory">
            <property name="mongoClientURI" value="mongodb://username:password@yourdomain.com:27017,username:password@yourdomain.com:27017"/>
Full instructions for this can be found in: https://stackoverflow.com/questions/25311699/custom-jndi-object-factory-in-wildfly-8-for-cdi

2. Start both EAP 6 and EAP 7;
3. Discover newly started EAP 6 and EAP 7 and add them to the inventory;
4. Navigate to JBoss ON UI -> EAP 6 resource -> Subsystem -> naming -> Bindings -> java:global/MongoClient resource -> Configuration tab -> and check what's visible there.

Actual results:
Visible fields are: Binding Type, Class, Lookup, Module, Type and Value. However, Environment and Cache fields are not there.

Expected results:
Everything should be visible - including Environment and Cache fields. 

Additional info:
Comment 1 Ruben Vargas Palma 2017-11-01 23:26:50 EDT
commit 704076e040f8410ba0b53e1753c1c4447ad5501b
Merge: 4eea9fc d574eaa
Author: Josejulio Martínez <finwemartinez@gmail.com>
Date:   Tue Oct 31 16:04:56 2017 -0600

    Merge pull request #333 from rubenvp8510/binding_env_eap6
    Bug 1477945 Environment and cache parameters added to subsystem=naming/binding fo…

commit d574eaab930e17f6b6fe1eaa37ca4758a9e527d9
Author: Ruben Vargas <rvargasp@redhat.com>
Date:   Mon Oct 30 22:53:02 2017 -0600

    Environment and cache parameters added to subsystem=naming/binding for EAP6
Comment 4 Filip Brychta 2017-11-16 09:13:47 EST
Missing fields are added but attempt to update Cache field fails with {JBAS014653: Composite operation failed and was rolled back. Steps that failed:={Operation step-7=JBAS011877: Binding type object-factory can not take a 'cache' attribute}}, rolled-back=true

Update of Environment properties works fine.

Issue is visible in both standalone and domain.
Comment 5 Filip Brychta 2017-11-20 06:52:01 EST
Discussed the issue with EAP QE. This behavior is expected. jboss-cli is showing all attributes for all binding types and keeps those which are not applicable for given binding type as undefined. Attempt to update attribute which is not applicable for given binding type fails. User is expected to only update expected attributes.

Marking as verified

I created new bz1515203 for missing external-context type

Note You need to log in before you can comment on or make changes to this bug.