File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes JBoss/WildFly and the fly likes partly beans Not Bound Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of REST with Spring (video course) this week in the Spring forum!
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "partly beans Not Bound" Watch "partly beans Not Bound" New topic

partly beans Not Bound

ray frid
Ranch Hand

Joined: Dec 23, 2010
Posts: 79
Hi all,
I am migrating Jboss 4 to Jboss 5.1AS.

There is some weird situation where part of my Stateless beans are not bounded.

this is the Exception as you all know it:

18:38:30,046 ERROR [STDERR] javax.naming.NameNotFoundException: LogDaoBean not bound
18:38:30,046 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(
18:38:30,046 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(

If we look at the server log we can find this error

Deployment "<UNKNOWN jboss.j2ee:ear=WMA_EXPLODED.ear,jar=WMA_EXPLODEDEJB.jar,name=LogDaoBean,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'persistence.unit:unitName=WMA_EXPLODED.ear/WMA_EXPLODEDEJB.jar#wmaPU' **

Any idea what could cause it?


I agree. Here's the link:
subject: partly beans Not Bound
It's not a secret anymore!