java ee - CDI doesn't work when ejb inject implementation define in war of same ear -
I have an EAR file that contains multiple ebay and war. In ejb-jar, I inject many implementations of such an interface like this:
@inject = any personal example & lt; Configuration Provider Local & gt; ProviderEjb; The implementation of this interface is defined in a war. It deploys the implementation properly.
glassfish in v3.1 log I see:
Infos: Portable JNDI for EJB FormConfigurationProviderBean Name: [java: global / com.dialog.edialog_eservices_ear_1.0.1 -SNAPSHOT /checkout-form-1.0-SNAPSHOT / Form Configuration Provider Bean, Java: Global / Com. Dialogue Adiyalog_sirvorsi_aiyr_lk0kl-Saanapisacoti / checkout-form -1.0-Saanapisacoti / form configuration provider Binkcomkaoelog. Sbsm.talisker.core.config.api.ConfigurationProviderLocal]
But my implementation in practice:
(for configuration provider local provider: providerEjb) {[...]} implementation FormConfigurationProviderBean Never does I have no messages in log in, which can explain this. The addition, when I deploy war stand alone am (within the inside of the intestines) injected with the inside embedded dependencies work correctly.
P> What is the CDI supported when the implementation is defined within a war? Is there a classloader issue?
The should do work, the right to provide setup (which Is probably the case). I had a similar problem with JBs World (AS6), where different artifacts did not see each other in an EAR. What I will do as to reconfigure the JBoss classloading- mechanism to solve it, but the field (and proprietary) JBoss was stuff
I first debugging step :. Queries about what beans are actually around It can give you a hint of a little bit of indifference that can be helpful only with initial bean processing.
It still looks like a CL-issue that you can find in the Glassfish documents for configuration options. Probably suitable for testing with glassfish developers if this is a known problem / problem ...
Comments
Post a Comment