atom feed7 messages in net.java.dev.glassfish.usersRe: embedded ejb container - CDI
FromSent OnAttachments
Phillip RossMar 11, 2011 8:23 am 
Laird NelsonMar 11, 2011 8:26 am 
Phillip RossMar 11, 2011 8:41 am 
Laird NelsonMar 11, 2011 8:52 am 
Phillip RossMar 11, 2011 9:57 am 
Phillip RossMar 11, 2011 10:25 am 
Phillip RossMar 11, 2011 11:00 am 
Subject:Re: embedded ejb container - CDI
From:Phillip Ross (phil@gmail.com)
Date:Mar 11, 2011 8:41:15 am
List:net.java.dev.glassfish.users

Thanks Laird I'll try that. Would you know offhand how logging levels are set/modified w/ embedded?

On Fri, Mar 11, 2011 at 11:26 AM, Laird Nelson <ljne@gmail.com> wrote:

On Fri, Mar 11, 2011 at 11:23 AM, Phillip Ross <phil@gmail.com

wrote:

Unfortunately there is no stacktrace shown to see under the hood of what's failing during container instantiation, and even though it says to see the log for details, there isnt actually a log file to check for the embedded ejb container. If I remove the beans.xml from the classpath things work fine. I actually stripped out all of the CDI code and still get the error whenever beans.xml exists, which makes me think just having weld fire up is what is causing the problem. Any ideas of how to troubleshoot this further?

Set logging levels to FINER. I set them like this:

javax.level = FINER com.sun.level = FINER org.glassfish = FINER

...(if I'm remembering right). You'll see more than you ever wanted to. :-)

Best, Laird