jaikiran/jboss-as — comment on commit 0b149eff7661321fc0a1ef7f2858c81b5c14f208
File: ejb3/src/main/java/org/jboss/as/ejb3/subsystem/EJB3SubsystemRootResourceDefinition.java line 60
By bstansberry:

This was in response to a question about a patch that changed expression
support for an attribute. Replying to the full jboss-as7-dev list as an
FYI to others:

On 10/11/11 10:56 AM, Jaikiran wrote:
> No specific reason against it. I wasn't sure what the convention was. Are we allowing expressions for most of the attribute values and only disallowing wherever it makes sense?
>

This has evolved a bit, so yours is a good question. The console guys
are actively pursuing supporting expressions, so that has removed a
barrier we had to being aggressive about allowing them. The fairly
recent AttributeDefinition stuff that the ejb3 subsystem and some others
is using also greatly reduces the chances of screwing them up, so we can
be more aggressive.

At this point we should support them anywhere it doesn't give you a
queasy feeling. ;) If you can think of an argument not to support them
someplace; fine don't. If you just have a sixth sense it's a bad idea;
fine, don't support an expression. We can always add support in a later
release, but we can't remove it. But otherwise, go ahead and support
it. Expressions will be very important in cloud use cases where
customizing the config file on a per-server basis is a poor option.

--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat