This looks like either oversight in the spec or there is something I don't understand…
There should at least be a warning in big letters that the datasource was not found,
instead of just silently defaulting.
Perhaps you should take this up with the spec guys for clarification.
My particular case is that with GF4, I am now forced to create glassfish-web.xml or glassfish-ejb.xml
to map the resources. If I don't, there is no way to configure the mapping using @Resource(name="xxx")
I thought Sun/Oracle wanted to be more standardized and eliminate glassfish-xxx files wherever possible?
With this change, there is no way to configure a resource without glassfish-xxx files.