Yes, please do. In the JBAS project. Actually, I see two issues in this thread:
1) Figuring out why the @Depends on your EJB results in a different error
message than the expected one that I got when I deployed my example POJO.
2) Coming up with a mechanism to avoid the ERROR message altogether
Shall I write up a JIRA ticket for this issue so that it shows up on the
appropriate radars?
We're getting ready to deploy to production with 5.1.0 so we're interested in
tracking this topic.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4241304#4241304
The DEPLOYMENTS MISSING DEPENDENCIES: error message is rather cryptic; I'm
looking into it to make sure it means what I think it means. But my
interpretation is not that the microcontainer expects the bean to be in
Described but rather that it doesn't recognize the name at all.
Looking at the
bstansbe...@jboss.com wrote : Hmm, a possibility here is the
BarrierController is directly registering the Barrier in JMX, and the
microcontainer is bypassed. So the microcontainer is unaware of the barrier.
OK, I checked that theory out and the microcontainer isn't bypassed; things
work as
I tried deploying a simple pojo with a dependency on the barrier:
| deployment xmlns=urn:jboss:bean-deployer:2.0
|
|bean name=Test
| class=java.lang.Object
|
| dependsjboss.ha:service=HASingletonDeployer,type=Barrier/depends
|
|/bean
|
|
Brian,
I was able to reproduce this with a simple SLSB:
import javax.ejb.Stateless;
|
| import org.jboss.ejb3.annotation.Depends;
|
| @Stateless
| @Depends(jboss.ha:service=HASingletonDeployer,type=Barrier)
| public class CalculatorBean implements CalculatorRemote, CalculatorLocal
Ah, did not see your 15:12 post, while typing my reply.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4240852#4240852
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4240852
___
Thanks for looking into this.
bstansbe...@jboss.com wrote : If you shut down the first node and the 2nd
becomes master, does the EJB deploy properly?
Yes, when I shut down node 1, the EJB does seem to properly deploy / start on
node 2 when it becomes the master. So it appears to work. What
