[
https://jira.jboss.org/jira/browse/JBSEAM-3248?page=com.atlassian.jira.pl...
]
Francisco Jose Peredo Noguez reopened JBSEAM-3248:
--------------------------------------------------
I think this problem should be handled by Seam, I posted a comment explaining why. I feel
that since the exception is prevented if I modify
org.jboss.seam.mock.EmbeddedBootstrap.startAndDeployResources then it should be Seam
responsibility to bootstrap Jboss in a way that either doesn't cause a crash, or sends
an exception with an easy to understand message saying that the Boostrap will fail before
it actually fails (Or maybe it should pre-load components.xml and somehow inform JBoss
that since the datasource is going to be managed by Spring, then it shouldt crash, after
all that is what it seems to be doing after I modified startAndDeployResources . Why am I
wrong?
If not using EJBs, and not using JNDI datasource (thanks to Spring)
then Seam Test fails with a hard to understand message
---------------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-3248
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3248
Project: Seam
Issue Type: Feature Request
Components: Test Harness
Affects Versions: 2.0.2.GA
Reporter: Francisco Jose Peredo Noguez
Assignee: Pete Muir
When developing Seam integration tests if you aren't deploying EJBs, then you
don't need the container to deploy archives which contain EJBs. But if you have
org.jboss.embedded.Bootstrap.class in the classpath, and you are using a datasource
configured with Spring (and without JDNI) you will get this error:
persistence.units:unitName=webappsbmi-test -> java.lang.RuntimeException:
Specification violation [EJB3 JPA 6.2.1.2] - You have not defined a non-jta-data-source
for a RESOURCE_LOCAL enabled persistence context named: webappsbmi-test
Instead of that, it should send an error saying something like:
"As you aren't deploying EJBs, then you don't need the container to deploy
archives which contain EJBs."
or
"As you you are not using a JNDI datasource then you can not use the container to
deploy archives which contain EJBs."
or something like that... I wasted a lot of time trying to find out what was happening
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira