AW: Wicket / WildFly 8: Log4J / SLF4J ?
Hi Sebastien, just a few final words abot my Wildfly experiences. 1. Any jar file that you want to use in your applicationsmust be defined as a module in subfolder "modules". If you want to use an oracle driver this must be a module 2. Modules that use other modules define this dependencies in their module.xml file e.g. 3. Using a module like the above one in a deployes JAR/EAR or WAR needs the "Dependencies=de.my.module" specification 4. modules with "export=true" are inherited by the JAR/EAR or WAR Now I think you have wicket.jar inside your WEB-INF/lib folder inside of your application.war file. Such jar files are available to your app without defining them as a module. But I don't know if e.g. wicket.jar needs a "Dependencies=org.apache.log4j etc" specification in it's MANIFEST.MF to have access tot he logging system. I did not try this. Mit freundlichen Grüßen --- Stefan Lindner, Visionet Hard- und Software GmbH, Karolinenstraße 52b, 90763 Fürth Durchwahl: Tel.: 0911/148894-10, FAX: 0911-148894-11, E-Mail: stefan.lind...@visionet.de Zentrale: Tel.: 0911/148894-0, FAX: 0911-148894-99, Internet: http://www.visionet.de Registergericht Fürth: HRB 6573, Geschäftsführer: Stefan Lindner -Ursprüngliche Nachricht- Von: Sebastien [mailto:seb...@gmail.com] Gesendet: Freitag, 8. August 2014 14:55 An: users@wicket.apache.org Betreff: Re: Wicket / WildFly 8: Log4J / SLF4J ? Hi Stefan, Thanks for your verification, it is really helpful. By conscience, I tried out the "full" profile, nothing better. I will investigate a little bit further and will post the answer (as supposed I find the answer... :s) Best regards, Sebastien. On Fri, Aug 8, 2014 at 2:32 PM, Stefan Lindner wrote: > Hi Sebastien, > > your file looks similar to mine. I can't remember any problems with > logging.Just worked out oft he box. Defining datasources, using own > libraries etc was a pain but logging was not. > The only difference between you and me: i use the "full" profile which > you might require to use too wehen you think about EJBs persistence, > message queues etc. > > --- > Stefan > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
AW: Wicket / WildFly 8: Log4J / SLF4J ?
Hi Sebastien,
your file looks similar to mine. I can't remember any problems with
logging.Just worked out oft he box. Defining datasources, using own libraries
etc was a pain but logging was not.
The only difference between you and me: i use the "full" profile which you
might require to use too wehen you think about EJBs persistence, message queues
etc.
---
Stefan
-Ursprüngliche Nachricht-
Von: Sebastien [mailto:seb...@gmail.com]
Gesendet: Freitag, 8. August 2014 14:12
An: users@wicket.apache.org
Betreff: Re: Wicket / WildFly 8: Log4J / SLF4J ?
Hi Stefan,
Many thanks for your answer; yes, that helps to know that it is supposed to
work out of the box!
I tried your suggestion - even if INFO would have been enough for now - without
more success.
I also added "Dependencies:
org.slf4j,org.slf4j.impl,org.slf4j.jcl-over-slf4j,org.apache.log4j" to the
manifest (I didn't had it), but nothing better unfortunately.
The generated logging.properties
(wildfly-8.1.0.Final/standalone/configuration) looks like this (see below).
Would it be possible that you compare with yours (if
handler.CONSOLE=org.jboss.logmanager.handlers.ConsoleHandler is the same for
instance)?
Many thanks in advance,
Sebastien.
loggers=com.arjuna,jacorb,org.apache.wicket,org.apache.tomcat.util.modeler,org.jboss.as.config,sun.rmi,jacorb.config,com.amadeus
logger.level=INFO
logger.handlers=CONSOLE
logger.com.arjuna.level=WARN
logger.com.arjuna.useParentHandlers=true
logger.jacorb.level=WARN
logger.jacorb.useParentHandlers=true
logger.org.apache.wicket.level=DEBUG
logger.org.apache.wicket.useParentHandlers=true
logger.org.apache.wicket.handlers=CONSOLE2
logger.org.apache.tomcat.util.modeler.level=WARN
logger.org.apache.tomcat.util.modeler.useParentHandlers=true
logger.org.jboss.as.config.level=DEBUG
logger.org.jboss.as.config.useParentHandlers=true
logger.sun.rmi.level=WARN
logger.sun.rmi.useParentHandlers=true
logger.jacorb.config.level=ERROR
logger.jacorb.config.useParentHandlers=true
logger.com.amadeus.level=DEBUG
logger.com.amadeus.useParentHandlers=true
logger.com.amadeus.handlers=CONSOLE2
handler.CONSOLE=org.jboss.logmanager.handlers.ConsoleHandler
handler.CONSOLE.level=INFO
handler.CONSOLE.formatter=COLOR-PATTERN
handler.CONSOLE.properties=enabled,autoFlush,target
handler.CONSOLE.enabled=true
handler.CONSOLE.autoFlush=true
handler.CONSOLE.target=SYSTEM_OUT
handler.CONSOLE2=org.jboss.logmanager.handlers.ConsoleHandler
handler.CONSOLE2.level=TRACE
handler.CONSOLE2.formatter=COLOR-PATTERN
handler.CONSOLE2.properties=enabled,autoFlush,target
handler.CONSOLE2.enabled=true
handler.CONSOLE2.autoFlush=true
handler.CONSOLE2.target=SYSTEM_OUT
# Additional formatters to configure
formatters=PATTERN
formatter.PATTERN=org.jboss.logmanager.formatters.PatternFormatter
formatter.PATTERN.properties=pattern
formatter.PATTERN.pattern=%d{-MM-dd HH\:mm\:ss,SSS} %-5p [%c] (%t) %s%E%n
formatter.COLOR-PATTERN=org.jboss.logmanager.formatters.PatternFormatter
formatter.COLOR-PATTERN.properties=pattern
formatter.COLOR-PATTERN.pattern=%K{level}%d{HH\:mm\:ss,SSS} %-5p [%c] %s%E%n
On Fri, Aug 8, 2014 at 1:40 PM, Stefan Lindner
wrote:
> Hi Sebastien,
>
> did you add
>
> Dependencies =
> org.slf4j,org.slf4j.impl,org.slf4j.jcl-over-slf4j,org.apache.log4j
>
> to your MANIFEST.MF?
>
> ---
> Stefan
>
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
AW: Wicket / WildFly 8: Log4J / SLF4J ?
Hi Sebastien, did you add Dependencies = org.slf4j,org.slf4j.impl,org.slf4j.jcl-over-slf4j,org.apache.log4j to your MANIFEST.MF? --- Stefan -Ursprüngliche Nachricht- Von: Sebastien [mailto:seb...@gmail.com] Gesendet: Freitag, 8. August 2014 12:27 An: users@wicket.apache.org Betreff: Wicket / WildFly 8: Log4J / SLF4J ? Hi all, Well, that's not a pure wicket question but maybe the answer (if any, I hope) could interest future readers... I am trying to set-up a new project using Wicket (7), WildFly 8 (and EJB-3.1, CDI-1.1, native websockets, and probably something that make the coffee...) but for now I am stuck because I don't have any logs in the output (console or file) coming from wicket itself or my wicket application. I read all the internet (twice...), some says that's is not possible to have log4j/slf4j in WildFly, some says it should be activated using jboss-deployment-structure.xml for instance, some says it's already bound by default just need to add a "logger category" in standalone.xml and having the log4j.property file in the ear/war. I tried everything but after 2 days, I am running out of ideas... So, does anyone have already deployed a simple wicket application onto WildFly ? Are the logs working ? Is there any hint to make it work ? Many thanks in advance, Sebastien. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
AW: Wicket / WildFly 8: Log4J / SLF4J ?
Hi Sebastien, I started Wildfly8 development with wicket a few weeks ago. At first: logging works and it seems that jboss still uses log4j wich is configured in standalone.xml/standalone-full.xml. Simply adding a logger category will not work because the log level in consele handler is restricted to INFO: You might define your own handler like And define Does this help? --- Stefan -Ursprüngliche Nachricht- Von: Sebastien [mailto:seb...@gmail.com] Gesendet: Freitag, 8. August 2014 12:27 An: users@wicket.apache.org Betreff: Wicket / WildFly 8: Log4J / SLF4J ? Hi all, Well, that's not a pure wicket question but maybe the answer (if any, I hope) could interest future readers... I am trying to set-up a new project using Wicket (7), WildFly 8 (and EJB-3.1, CDI-1.1, native websockets, and probably something that make the coffee...) but for now I am stuck because I don't have any logs in the output (console or file) coming from wicket itself or my wicket application. I read all the internet (twice...), some says that's is not possible to have log4j/slf4j in WildFly, some says it should be activated using jboss-deployment-structure.xml for instance, some says it's already bound by default just need to add a "logger category" in standalone.xml and having the log4j.property file in the ear/war. I tried everything but after 2 days, I am running out of ideas... So, does anyone have already deployed a simple wicket application onto WildFly ? Are the logs working ? Is there any hint to make it work ? Many thanks in advance, Sebastien. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
