SeamTest is one of the reasons we switched from @EJB to @In ;-)
I have been able to get EJB3 & hibernate work with testNG based on the
examples. But, I am unable to get Hibernate & EJB3 working in the same test.
The errors include datasource not defined even though it is defined in
jboss-beans.x
You'll have to ask bill about JAAS support.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3935799#3935799
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3935799
---
T
anonymous wrote : I am trying to get a SeamTest running which uses a JBPM
process,
|
| Yes, I didn't get this working yet :-(
a partial solution is to test the JBPM separately, but it fails if there are
dependencies on SEAM components in the process definition.
For that I use a MockVariabl
"d1g" wrote : I'm also keen on embedding Seam & JBoss EJB3 as I think I'll end
up writing scripts in BSH to do disposable script stuff (maintenance).
|
Actually I was thinking of shipping Seam with beanshell integration so you can
dynamically call Seam components from the console. Would make
"mk74" wrote : I am trying to get a SeamTest running which uses a JBPM process,
Yes, I didn't get this working yet :-(
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3935621#3935621
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode
I am pleased that the test functionality exists and we'll certainly be
implementing tests further into development. Ideally we would have been
implementing tests up front but this is hard when we're still learning Seam,
JSF, EJB3, etc. I would imagine that any subsequent projects will involve us
I am trying to get a SeamTest running which uses a JBPM process,
but I get an exception when I try to retrieve a SEAM component with:
@Override
protected void invokeApplication() {
Register c = (Register) Component.getInstance("register", true);
}
The co
We started off using it (and it worked quite nicely). But as always the
development continued without the test cases being kept in sync (or not even
writing integration tests for stuff that needs to be developed). As a result
our integrations tests are completely useless (for that matter also ou
The "comp not bound" problem is a name not found exception coming from JNDI
when there is no java:/comp namespace in JNDI.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=398#398
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&
I'll be using SeamTest for integration testing of each main line use case
scenario at least. I've opted not to use the EJB bootstrap component though, &
boot the EJB3 standalone using a beforeSuite @Configuration. Speed is the issue
for me, though I think the EJB component will be very handy for
I found a workaround for this problem.
UIViewRoot had same ID then first component. So I did following:
Changed start of debug.xhtml as follows:
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
http://java.sun.com/jsf/facelets";>
http://www.w3.org/1999/xhtml";
xmlns:f="http://ja
We have used it, but it just isn`t neccessary usually. Because monitoring is
enough.
Btw. our debug page does not work anymore. Client-id is duplicated in faces
tree. Upgraded facelets & myfaces but no use. Do you have any suggestions Gavin?
View the original post :
http://www.jboss.com/index.h
12 matches
Mail list logo
