yes I guess that could work I might try this as well even though changing the
Seam code to speed up the tests is not my preferred solution ..
jens
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3981287#3981287
Reply to the post :
Hi there,
I have some question concerning integration tests with Seam.
1) I have the impression the MDB configuration is not picked up by EJB
bootstrap initiated through SeamTest. On container startup I get an
DefaultJMSProvider not bound error
If I bootstrap the EJB container myself and
I resolved issue 1) now. I had to copy the content of jboss-jms-beans.xml into
jboss-beans.xml so it gets picked up by SeamTest. That means
jboss-jms-beans.xml in the Seam embedded-ejb/conf folder is not read on
container start-up though.
Jens
View the original post :
I bootstrapped it the container on its own as well. But if you test several
SeamTest classes it will still rescan the components every time and complain
about several phase listeners, right?
Ok it comes to question 3) then ..
Jens
View the original post :
problem solved. I used my own seam jboss-seam.jar debug version. It didn't
include the faces-config.xml which I was surprised to find in the original jar
archive ...
Jens
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3967647#3967647
Reply to the post :
Hi there,
how does this automagical creation work? I have declared a component and try
to call it from the declaration in pages.xml and get the same error.
It works when I outject a component to a context. But at the end I want to have
a stateless bean created whenever requested.
I lack a bit
Thanks for the quick answer.
I'll post the remoting bug on JIRA once I figured out where to find that.
Maybe it wasn't clear but I do use a stateful session bean not stateless.
@PersistenceContext is injected, @Logger is not.
Jens
| @Startup
| @Name(dbCache)
| @Stateful
|
Hi,
logger is not injected on a stateful bean either. Somehow I feel Seam
annotations are not correctly processed for @Startup components.
Would like to know as well if anyone has an idea why @Create works on stateless
beans?
Thanks a lot
Jens
[Btw, if anyone from Jboss listens,