I've noted that SocketUseSSL is not respected in c++. I have a quickfix engine (acceptor) with ssl. And I am trying to connect to it via quickfix c++. I added SocketUseSSL=Y property to the config file but it is not respected.
Are there any other properties I need to use in conjunction with the SocketUseSSL ?
I wrote my own ssl proxy with openssl but I was checking just in case if we can use this option.
I managed to answer my own question.
There are no SocketUseSSL property in config file for quickfix c++ as of now. I logged https://github.com/quickfix/quickfix/issues/31 to address the issue.
Related
I'm trying to use a properties file not included in the app but specify it as a Java option during invocation.
something like
java -Dconfig.file=run.properties -jar app.jar
I am looking for suggestions on how can I send that property to ScalatraBootstrap when the app initializes.
Thanks
3
I figured that this is only possible if I use
com.typesafe.config.ConfigFactory
I am using RSE to connect to a Linux RDT server. I connect through SOCKS (SSH tunneling from another machine) but that's not the issue, because I have the same problem when I connect directly (when I am in the same LAN).
The settings are pretty straightforward, and I can connect to the remote project and save files.
However, when I try to build I have:
Error: Program "rm" not found in PATH
Needless to say, the environment variable PATH is defined and yes, it points to /bin among others.
Anyone can guess what's the problem here?
After that, I have a can not clean programmatically: build workspace path is not specified message.
Why don't you simple use absolute pathname? /bin/rm
also ' ' (spaces) in PATH could give you problems.
Is there a way to fix the file locking issue caused by jetty entirely from gradle?
Some clarification:
When using the Gradle Jetty plugin by running gradle jettyRun, jetty causes the static resource files (html, css, js, etc.) to be locked when using Windows.
You can see a description of the problem in Files locked on Windows.
The same article also describes how you can fix that. Basically you have to either:
Disable the use of file mapped buffer
Not use NIO at all.
Both things require to add some jetty specific configuration files to the project, which I do not want to do - the jetty plugin is used only for convenience, and maintaining configuration for it does not feel right.
I do not need NIO for testing on the local machine, so any solution works.
Edit:
For now, I picked the option at which you set useFileMappedBuffer to false. This is how to do it:
Specify a path to your webdefault.xml like
[jettyRun, jettyRunWar,jettyStop]*.with {
//other configs
webDefaultXml = file("${project.webAppDir}/WEB-INF/jetty-webdefault.xml")
}
Get file from the latest 6.1.x distribution of jetty. The plugin seems to support only jetty 6. You can localte it at jetty-6.1.26\etc\webdefault.xml. Obviously, you have to place it at the path specified at the previous step.
Change the default servlet init parameter useFileMappedBuffer to false
I will research the option of using embeded jetty insted of the plugin.
I found a plugin that seem to be a better alternative:
https://github.com/akhikhl/gretty
Positives
Does not lock your files and support hot deployment (even something Gretty call "fast reload")
Gretty 1.2.0 uses Jetty 9.2.9.v20150224. Jetty plugin provided by Gradle 2.2.1 uses Jetty 6.1.25.
same task is used jettyRun (or more simply run).
"Press any key to stop the server". Jetty plugin required CTRL+C then Y.
From what I can tell, the documentation seem to be awesome (Gradle's not so much)
Negatives
A bit more bloated code to setup the buildscript's classpath dependency or apply plugin directly from URL (see doc)
Gretty crash unless you explicitly apply plugin: 'war' (Jetty plugin extends the War plugin)
Kiril answered his own question, many thanks. You should follow Kiril's instructions and this will help you find the appropriate webdefault.xml.
To find out what version of Jetty is started by Gradle, execute
gradle jettyRun -i
And you'll see something like this:
...
Tmp directory = determined at runtime
Web defaults = org/mortbay/jetty/webapp/webdefault.xml
Web overrides = none
Webapp directory = C:\dev\my-project\src\main\webapp
Starting jetty 6.1.25 ...
jetty-6.1.25
...
It took me a while to find a copy of Jetty 6.1.25 as it is no longer listed on the Jetty download page (not even in the archive section!).
You can then grab the appropriate copy of webdefault.xml from here, adjusting the version number as appropriate for your needs:
http://grepcode.com/file/repo1.maven.org/maven2/org.mortbay.jetty/jetty/6.1.25/org/mortbay/jetty/webapp/webdefault.xml
I have tried this solution:
Open sitecore media library programmatically from asp.net button click
but this is not working for me. This gives a JavaScript error for .ascx file code mentioned in answer.
This statement: Sitecore.PageModes.ChromeManager.postRequest
I am using Sitecore 6.3, included sitecore.js file. But get the script error the PagesMode ChromeManager property caught for undefined.
Also tried to use
scForm.postRequest("", "", "", 'contentimage:open(id=FIELD1377303253)');
but this certainly wont issue the custom MediaBrowser command created for original solution.
Try to use the Sitecore.Shell.Framework.Windows.RunApplication() function. You need to pass the Media Library itemId as parameter in the RunApplication() method.
You can get the Media Library ItemId in the Core Database at the following path: /sitecore/content/Applications/Content Editor/Applications/MediaLibraryForm
Thanks
I am trying to use Qt 4.8 for proxy resolution, when I have a proxy set in the system configuration under Windows.
My question is that when I set my system settings to use a PAC file, I can use the QNetworkProxyQuery and QNetworkProxy classes to resolve that PAC file for a given domain. However, is there a way I can obtain the actual PAC file contents itself using Qt functionality (or even just the location of the PAC file that is specified in the system settings), rather than have Qt resolve it for me? I know I can use Qt calls to pull down the file manually, but I would have to get the location of the PAC file first as well.
Regards,