Show Table of Contents
3.3.8. JBoss AS 7 and EAP 6 - Naming Service
Overview
Table 3.383. Overview
| Description: | |
| Singleton: | yes |
| Plugin: | JBossAS7 |
Child Resource Types
Connection Properties
Table 3.384.
| Name | Description | Required | Internal Name |
|---|---|---|---|
| Path | yes | path |
Note
You must use the internal name to reference Configuration Properties in Dynamic Group Definition expressions.
Metrics
none
Configuration Properties
none
Operations
Table 3.385. Metrics
| Name | Description |
|---|---|
| JNDIView | Peek at the JNDI tree |
Package Types
none
3.3.8.1. JBoss AS 7 and EAP 6 - Binding Service
Overview
Table 3.386. Overview
| Description: | JNDI bindings for primitive types |
| Singleton: | no |
| Plugin: | JBossAS7 |
Child Resource Types
none
Connection Properties
Table 3.387.
| Name | Description | Required | Internal Name |
|---|---|---|---|
| Path | yes | path |
Note
You must use the internal name to reference Configuration Properties in Dynamic Group Definition expressions.
Metrics
none
Configuration Properties
Table 3.388.
| Name | Description | Required | Internal Name |
|---|---|---|---|
| Binding Type | The type of binding to create, may be simple, lookup or object-factory | yes | binding-type |
| Class | The object factory class name for object factory bindings | no | class |
| Lookup | The entry to lookup in JNDI for lookup bindings | no | lookup |
| Module | The module to load the object factory from for object factory bindings | no | module |
| Type | The type of the value to bind for simple bindings, this must be a primitive type | no | type |
| Value | The value to bind for simple bindings | no | value |
Note
You must use the internal name to reference Configuration Properties in Dynamic Group Definition expressions.
Operations
none
Package Types
none

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.