I agree with Henk,
we use resource definition templates (DS, JMS) in our EARs frequently. This makes sense since their names and most of the configuration details are application specific and maintained by the developers. Plus, we dont want to rely on expert or application-specific knowledge at the customer side where the applications are deployed. So we provide this template and simple skipt-based property replacement (basically for ds-urls).
Yet, we provide our resource definitions as .sar archives (jboss-service.xml). So will this approach still be supported?