Details
Major Description
The cdi spec and pete muir are a bit unclear on how many web beans contexts there are for an ear. At the moment the behavior is ridiculous: the ejb module sets one up using the openejb lifecycle (good) and then the web module sets one up for the same classes using the web lifecycle (bad). At least until we understand what is supposed to happen and have separate bundles for each module the best solution (IMO) is to have a single web beans context for the entire ear, set up by openejb. This involves a slight change in the existing sharing logic.