+++ This bug was initially created as a clone of Bug #1515201 +++ Description of problem: Following types of binding are available in EAP: simple object-factory lookup external-context but JON only supports: simple object-factory lookup Version-Release number of selected component (if applicable): JON 3.3.9. EAP plugin pack 05 How reproducible: Always Steps to Reproduce: 1. Navigate to JBoss ON UI -> EAP 6 resource -> Subsystem -> naming -> Create Child -> Binding 2. File name and click on Next Actual results: Only simple, object-factory and lookup binding types are available. Expected results: All 4 binding types should be supported Additional info: You can list all supported binding types e.g. in jboss-cli: /subsystem=naming/binding=java\:global\/a:read-resource-description
You can create simple binding following way: /subsystem=naming/binding="java:/global/a":add(binding-type=simple, value=100)
Available in the master: commit 85af3a37d6733a44de4ea4462260b33f77043bb5 (HEAD -> master, upstream/master) Author: Michael Burman <miburman> Date: Fri Nov 9 14:25:22 2018 +0200 [BZ 1515201] Add external-context to EAP6 plugin as a naming binding option
Previous one is wrong commit, this is the correct for EAP6: commit 7219c74f89ef0ad8a20088cd73ed6f233eadd499 Author: Michael Burman <miburman> Date: Fri Nov 9 14:22:44 2018 +0200 [BZ 1515203] Add external-context to EAP6 plugin as a naming binding option
Moving to ON_QA. See https://bugzilla.redhat.com/show_bug.cgi?id=1543522#c1 for test setup gory details.