I try to use flogger with the log4j2 backend. Seems to work fine.
My problem is, how to configure output pattern, output level or appenders in general using log4j files (xml or properties).
If using this constellation without any configuration, only level error is logged.
OK, I missed to add log4j-web package, so everything was fine in a standalone app, but this package is needed in a web application
Related
I have a .NET MVC application that includes a web service.
I have added Swashbuckle to the web service project and on my local machine everything works fine.
When I move the code to our TEST environment I begin to get 404 errors randomly for the various javascript and CSS libraries.
Sometimes the swagger/ui/index page itself throws a 404. Sometimes everything loads.
I've thought about downloading all of these files and placing them in my project for Swagger to use, but based on what I've read, and the way my local environment works, it doesn't seem like that's the way swashbuckle is designed to work, so I'm at a loss.
I have very limited access to the TEST environment so any server configuration will be an issue. My hope is that swagger.config file can be updated to make everything play nice.
I discovered that my TFS build server was NOT overwriting the previous build which led to differences between my load balanced servers and files that were not being updated with changes as I tried to get Swashbuckle to work.
We are working on adding custom level logging into our logger (which is currently log4j 1.2.x) and understood that this functionality is supported since log4j 2.
Thus we are planning to migrate from log4j 1.2.x to log4j2 version. However, our logger application is completely dependent on the log4j 1.2.x appenders where we directly extend / inherit appender classes like FileAppender etc. Right the bridge dont have support for the individual appenders and we are using the appenders in our application to log data.
Is there any way that those classes (which are dependent on FileAppender) can be readily migrated, because I dont see much information in internet / apache.org to get the internals.
Appreciate your help.
Thanks.
I am working in Grails 3.0.9 application and I am creating services and controller in default package. I want to log them with my logger but logger asks for the package name. I want to show the logs on All level from application. I set root logger as All and booom it shows whole grails framework logs. I want only my application logs. Please suggest me a good solution for my logging problem.
Move your classes to packages.
I have been handed a .WSDL file which I need to test within a Grails Framework.
Any suggestions how to go about this.
Take a look at the http://grails.org/plugin/cxf and http://grails.org/plugin/cxf-client plugins. They're easy to use and backed by Apache CXF - https://cxf.apache.org/
The client plugin has a wsdl2java script that will generate code that you can use in your Grails app.
You could start with documentation itself: http://grails.org/Calling+External+WebServices
I'm writing a Grails app which I'd like 3rd parties to augment at runtime. Ideally they would be able to add a JAR/WAR to the webapp directory which contains new domain, controller and service classes, new views, and other content.
Is there a simple way to do this within grails? Would it be simplest to create a startup script which copies the new classes etc. into the relevant directories and then updates grails.xml and web.xml?
You will be able to do this in version 2 of grails in which plugins will be also OSGI plugins http://jira.codehaus.org/browse/GRAILS/fixforversion/15421
It seems that the Grails plugins will actually fit quite well for this: http://www.grails.org/Understanding+Plugins
A plugin can do just about anything... One thing a plugin cannot do though is modify the web-app/WEB-INF/web.xml or web-app/WEB-INF/applicationContext.xml files. A plugin can participate in web.xml generation, but not modify the file or provide a replacement. A plugin can NEVER change the applicationContext.xml file, but can provide runtime bean definitions