Re: CODI - turn off startup config logging?

hi, see CodiCoreConfig#isConfigurationLoggingEnabled regards, gerhard http://www.irian.at Your JSF/JavaEE powerhouse - JavaEE Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/12/1 oversteer brendanhealey...@yahoo.co.uk Hi, can

Re: CODI - turn off startup config logging?

I'm afraid I'm non the wiser for this - do I extend CodeCoreConfig and override the function? If so does this need to be in an @ApplicationScoped bean? Do I need any other annotations like @Enhanced or @Advanced? is there anything else I need to do to ensure that the overridden method is called

Re: CODI - turn off startup config logging?

hi, that depends on your environment (in combination with owb it's easy [1] and in combination with weld it's more complex and depends on the version you have to use) - see [2]. regards, gerhard [1] http://goo.gl/zsFfe [2]

Re: CODI - turn off startup config logging?

Gerhard, I'm a glassfish 3.1.1 user, so stuck with weld. I tried @Specializes with no luck. Maybe I need to stick with the logging! Gerhard Petracek wrote: hi, that depends on your environment (in combination with owb it's easy [1] and in combination with weld it's more complex and

Re: CODI - turn off startup config logging?

esp. for weld we have the alternative implementation modules. you can use them to provide custom implementations (e.g. [1] and [2]) or you are using the alternative config modules which use btw. need the alternative implementation modules (- you can use something like [3]). regards, gerhard [1]

Re: CODI - turn off startup config logging?

In glassfish the best solution is to just use mvn dependency:unpack-dependencies into your target/classes before building the war. Then exclude all jars from WEB-INF/lib. See https://issues.jboss.org/browse/CDI-18 and other issues with BDAs. LieGrue, strub - Original Message -