What's the reason that a perfectly fine feature as defining data sources in an EAR is going to be removed? Is this technical or because it's deemed to be a wrong approach to put a data source configuration inside an EAR?
And what about other resources like JMS queues, can they still be defined inside an EAR? Currently our apps define quite a number of queues that are each nothing more than e.g.:
<queue name="aQueue">
<entry name="/queue/aQueue" />
</queue>
I'm all for separation of concerns where it makes sense, but I see zero value in forcing resources like these JMS queues to be defined externally.