I have created jira task for this and scheduled for Oct 6 release.
You can watch to know when this bug is fixed. Unfortunately, RC2 is already packaged for release on Monday.
Some thing you want to try is put the -ds.xml file in the .par. Does that work?
No still not working (put it in root of .par and in META-INF)
AFAK it was always a problem with "packaged" datasources. Always had to set up dependencies but don't know how to do it with the Entity Manager. I think in general "packaged" datasources should be initialized first, what shouldn't be the problem b/c the "driver" must be placed in $server/lib anyway.
What is the status of this issue?! Is this resolved and is it now possible to deploy packaged datasources inside the ear?! Or is it neccessary to deploy them outside?
it is scheduled for next relesae. I'm working on it.
So how to setup connection to DB?
Don't know if it may help but the problem is the following:
init(...) create(...) start(...)
The deployment order (050:.deployer,...) is only used within a method
DS: datasource is bound in the start(...) method
EJB3:entity manager is set up in the create() method
create(...) NOK as DS is not yet bound
should be fixed in the next release. Just did some work in this area.
Any word on the progress with this bug? I have the same issue where I have a .ejb3 and a .par inside a .ear. There are some classes in the .ejb3 that have dependencies on the entity manager created by the .par. The ejb3 is always deployed first no matter how I declare it in the application.xml.
No need to ask here for further information. As stated above by Bill it is STILL listed at JIRA http://jira.jboss.com/jira/browse/EJBTHREE-296
Simply register/log in and watch it. And even better vote for it.
I have finished this in CVS HEAD, but have not adequately tested that it works correctly.