I think that some improvements have been made in deployment error handling that should show up in the final AS 7.0 release. I think that you could grab a nighly build from http://community.jboss.org/thread/167590.
If that doesn't help, we can probably try enabling TRACE logging and share the server.log here.
Actually, the original post was http://community.jboss.org/message/614269#614269
If you could give a few more details about your app, that would be helpful. I would like to see the persistence.xml that you are using (this will help me better understand). Even better if you could put a test case together that represents your seam3 app.
Regarding packaging Hibernate 3 jars with the app, I would like to make that work better also. I'll let you know when some code changes are available that might help.
Thanks Scott. I started working yesterday on doing a bare-bones application that demonstrates this that I can share so I don't accidentally paste company code. I should have it done by tomorrow.
Okay, after some more digging, here is what was going on here. We had a jar that contained a persistence.xml with a transaction type of RESOURCE_LOCAL and no jta-data-source or non-jta-data-source defined. The jar contains a module that instantiates hibernate independantly of the application server, so it simply uses the hibernate.connection.* properties in order to get the connection information and doesn't need a datasource.
It seems like the only difference is that JBOSS 6 doesn't scan jars in the claspath looking for persistence.xml where as JBOSS AS 7 does.