Re: [jboss-dev] Embedded Jopr snapshot included in the build!
IMO, logs like the following should be at DEBUG, isn't it:
19:22:46,251 INFO [Component] Component: resourceConfigurationUIBean,
scope: CONVERSATION, type: JAVA_BEAN, class:
org.jboss.on.embedded.ui.configuration.resource.ResourceConfigurationUIBean
...
19:22:46,507 INFO [SeamFilter] Initializing filter:
org.jboss.seam.web.redirectFilter
...
19:27:23,035 INFO [Contexts] starting up: org.jboss.seam.web.session
I'm not sure about this one:
19:22:44,825 INFO [Initialization] two components with same name,
higher precedence wins: org.jboss.seam.core.resourceLoader
This could be logged at INFO (if necessary) but the current message does
not tell me (the end user) much about what it's complaining(?) - unless
maybe i do a google and reach some FAQ.
-Jaikiran
Chris Bredesen wrote:
Dimitris Andreadis wrote:
> Pete Muir wrote:
>> Hi Dimitris,
>>
>> Not quite sure how you would do it I'm afraid - the obvious way
>> would be to allow the application to bundle it's own log4j.xml file
>> which overrides the AS one, but that doesn't seem to work in the
>> current code base. Want me to file a feature request?
>>
>> But I do believe Seam is using log levels consistently with JBoss AS.
>
> AFAICT, Seam is very noisy. Most of the info I'm trying to avoid
> should be logged at DEBUG level.
>
> Jaikiran proposed to still log this info, but only to the server.log,
> not the console.
+1 on logging only to the file. Most of that stuff does fit INFO IMO.
-CB
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development