Log4j2 accepts:
-Dlog4j.configurationFile=path/to/log4j2.xml
#see https://logging.apache.org/log4j/2.0/faq.html
But we used to be able to use a real URL like http://host/configuration.xml.
Is there a way to achieve this or has it been removed forever?
-Dlog4j.configurationFile actually accepts URLs as well.
You may want to raise a feature request for this on the log4j2 Jira issue tracker.
Related
I am developing one automation testing framework for a web application testing. For this automation framework I want implement logging with log4j2.
In web I found that there is 4 different way to configure the log4j2 configuration
1) .xml
2) .yml
3) .properties
4) .json
I am confuse which configuration will be better for which purpose. Can anyone explain me for what kind of application/situation which configuration is suitable.
Also I want to know how I can implement log4j2 from start to end (any link)
You're completely free to use any! It's a matter of personal preference.
You can see that they have the same capabilities in the configuration documentation.
A properties file is definitely the simplest, but there's probably more documentation using XML. YAML is much richer, I would start with either properties or XML.
Recently I got the error "automation server can't create object", for which I know the solution is to add your website to trusted sites and enable the setting: "Initialize and script ActiveX controls not marked as safe for scripting". But since this is a security issue, I searched for an alternative workaround but came up with nothing.
So, I am wondering if there is any other work around for this?
Please look at this SO question. Check if you did everything that was discussed there.
The first thing is to implement IObjectSafety interface. Then sign the activex and installer and CAB. You might also want to look at this example how to implement an activex.
I'd like to place all the #QueryParams inside a #BeanParam object and further document there. Is this possible?
currently not supported, but you could open a ticket here to see if it can be added
There is a ticket related and provided a patch. However the patch is based on the opener's private swagger branch. The change is very simple so it's easy to make a patch.
https://github.com/wordnik/swagger-core/issues/532
According to change log this feature was added in 1.3.5 version.
https://github.com/wordnik/swagger-core/wiki/Changelog#v135---apr-28-2014
Can confirm that this works with Jersey2 and swagger-jersey2-jaxrs_2.10. Just remember to annotate the properties in the #BeanParam target class.
I was wondering if Jira's REST API supports the ability to add an attachment to an issue (existing or new) along with uploading the attachment too? Looking at the API documentation I did not see anything however maybe i missed something.
This looks like the method you're after:
http://docs.atlassian.com/jira/REST/latest/#id339692
After you create the issue, you can click on more actions tab of that particular issue.
You would be able to attach files and attach screenshot.
Correct me if I am wrong in understanding your requirement.
Thanks.
in Python:
jira = JIRA(options="Jira_Server_URL", basic_auth=("userID", "Password"))
jira.add_attachment(issue=issue, attachment="attachment_path")
Replace Jira_Server_URL, userID, Password and attachment_path accordingly.
If I externalize part of my Grails configuration, must I restart my container for the change to be found? Is there any workaround to this if so? Thanks.
No, there's no automatic watch for changes to external config files. There's a good solution here that involves making a controller request to trigger a reload: http://jetlet.blogspot.com/2011/02/reload-external-config-file-dynamically.html
There's also this plugin, which looks like it hasn't been updated in a long time and may not work: http://www.grails.org/plugin/reloadable-config
Chiming in late here, but there's also
http://www.grails.org/plugin/external-config-reload