When a bean gets deployed in OpenEJB, it gets associated with a particular
container. Subsequently, that container may not be configured in that
instance of the server. When the server loads the Jar with the deployed
beans, it places beans in the containers that the beans were configured
with. Here, the bean BAR wants to go into the container FOO, which is not
currently configured.
This message is displayed when the server is starting up.
Cannot find bean "FOO" referenced by bean "BAR".
When a bean gets deployed in OpenEJB, it may contain references to other
beans. Subsequently, those beans may not be configured in that instance of
the server. When the server loads the Jar with the deployed beans, it
stores those references to those beans. Here, the bean BAR references FOO,
which is not currently configured in the JNDI namespace.
This message is displayed when the server is starting up.
This message is usally the result of a deployment descriptor that has been
created by hand.
Any help with the documentation is greatly appreciated.
All edits are reviewed before going live, so feel free to do much more than fix typos or links. If you see a page that could benefit from an entire rewrite, we'd be thrilled to review it. Don't be surprised if we like it so much we ask you for help with other pages :)
NOTICE: unless indicated otherwise on the pages in question, all editable content available from apache.org is presumed to be licensed under the Apache License (AL) version 2.0 and hence all submissions to apache.org treated as formal Contributions under the license terms.