arjan tijms wrote:
Jason, thanks for the replies. I'm still curious for answers to my earlier questions: is the reason for wanting to remove this feature technical and does it only concern data sources or also JMS queues, mail configs, etc?
Yes one of the big complaints we had with AS was that it was difficult to know what the actual server configuration was because it was spread out across many different files, some in deployments some not. Also those files intermixed system internals, wiring, and actual config. So a key design principal for 7 was to unify configuration in a consistent manner in one central place. You know exactly what resources are in use, what all the things you can tune are, and what you can lock down because you have one place to look. Also another requirement was that anything you can configure you can manage remotely via scripting languages, java clients, and a CLI. Deployment driven resources contradict all of this. So that's why we didn't plan on supporting them much beyond what the spec requires.
To answer your second question, yes this applies to jms queues, and any other globally manageable resource as well.
We certainly aren't against adding support for unmanaged deployed resources as a development-time feature. This is how we see the EE DataSourceDefinition support we already have being used. Since that can already be used for datasources, adding deployable JCA datasources isn't a high priority, so likely won't make 7.0. This could of course change if someone wants to help contribute a decent implementation.