This content has been marked as final.
Show 2 replies
-
1. Re: session bean not deployed
swd847 Apr 17, 2012 5:39 AM (in response to benitojuarez)The most likely cause is that the Logger class cannot be found, and this is causing a NoClassDefFound error when weld attempts to load the class.
-
2. Re: session bean not deployed
benitojuarez Apr 17, 2012 6:00 AM (in response to swd847)do i have to guess or is it possible to have a detailed log output. The server must have a reason to refuse my bean. Why doesnt it output anything?
A NoClassDefFound-Exception is theoretically possible, so i added a jboss-deployment-structure.xml to the ear-project, (path EarContent\WEB-INF). It had no effect.
<jboss-deployment-structure>
<deployment>
<dependencies>
<!-- Add dependency on log4j, this is not automatic dependency, it has to be explicitly defined, like follows: -->
<module name="org.apache.log4j" />
</dependencies>
</deployment>
</jboss-deployment-structure>