AFAK we currently only do system property substitution when we parse XML config files. As part of creating the metadata for a deployment, shouldn't we do it for any applicable type of metadata, e.g. annotation attributes of type String?
There have been requests for property substitution on annotations (see http://jira.jboss.com/jira/browse/EJBTHREE-424). I'd like to be able to do something like this:
@Target(ElementType.TYPE) @Retention(RetentionPolicy.RUNTIME) public @interface Clustered { Class loadBalancePolicy() default LoadBalancePolicy.class; String partition() default "${jboss.partition.name:DefaultPartition}"; }
Yes, we need to expand the existing asbstract helpers to include the current javaee5 annotation processing in the ejb3 deployer into a common annotation metadata deployer that adds support for replacement.