Neo Anderson wrote:
However, I encounter a new question. I use test case to call my ejb application (stateless session bean). Thus I found out when executing command 'mvn clean install,' it will do test first, resulting failure because the ejb artifact is still not yet deployed to the server. H
age
From: VUB Stefan Seidel <[EMAIL PROTECTED]>
To: Maven Users List
Sent: Monday, 3 March, 2008 9:49:25 PM
Subject: Re: javax.naming.CommunicationException: Receive timed out
problem
Hi,
this is most likely not a maven problem. It seems your test tries to
connect to a remote JBoss
launch the
server first before the test case executed.
Thanks in advice.
- Original Message
From: VUB Stefan Seidel <[EMAIL PROTECTED]>
To: Maven Users List
Sent: Monday, 3 March, 2008 9:49:25 PM
Subject: Re: javax.naming.CommunicationException: Receive timed out problem
Hi,
thi
Right, this is not a maven thing. JBoss didn't start. Simply put
JBoss doesn't do embedded testing like OpenEJB does, they require a
lot more setup and configuration to get going. There are a lot of
JBoss (or Glassfish, etc.) users who use OpenEJB for their build time
testing as it's a l
Hi,
this is most likely not a maven problem. It seems your test tries to
connect to a remote JBoss instance but cannot contact it (not deployed?).
regards,
Stefan
Neo Anderson wrote:
Hi
I am new to maven. And by following http://openejb.apache.org/3.0/simple-stateless-example.html I write
Hi
I am new to maven. And by following
http://openejb.apache.org/3.0/simple-stateless-example.html I write a simple
stateless session bean (ejb3) to test the jboss and maven,but encounter a
problem. The error issues
testHelloRemote(net.sf.sample.HelloTest) Time elapsed: 5.06 sec <<< ERROR!
