I am exploring the AWS X-ray for monitoring my application with java 7.But in documentation, I found that, It requires java 8 or later(https://docs.aws.amazon.com/xray/latest/devguide/xray-sdk-java.html).
Java 8 is required to up the xray or applicaton is needed to build in java 8?
If there is some process by which xray can be used with java 7?
There is no easy way to support Java 7. The SDK is developed on Java 8 which uses some features not available on older versions. You can download source from https://github.com/aws/aws-xray-sdk-java, modify it so it builds on Java 7 and use the built artifacts as needed.
Related
My application is hosted with JAVA 7. Hence need to have code sample for which is samples is with JAVA 7.
I can see the code with JAVA 8 or above.
https://github.com/Azure-Samples/ms-identity-java-desktop
How to exclude the org.json version in MULE 3.9.0 buildpath?
The version is json-20140107 I want to use the latest json version. I tried to exclude in mule-commons but it did not do any help.
The json-20140107.jar library is distributed with Mule 3.9.0. Because of how Mule implements classloading, at execution time classes loaded from that jar file will override a newer version in your application. You must not change the version provided because Mule was tested. Changing any provided library in the distribution can cause unexpected errors.
You could pack a new version of the library and try to use Fine Grain Classloader Control however that seems to be an Enterprise Edition feature not available in the community edition. If you have the Enterprise Edition it is highly recommended to use the last patch version (currently 3.9.4) instead of 3.9.0.
Another solution could be to migrate to Mule 4.x, which uses classloading isolation to avoid this kind of issues. You can use any version of libraries inside applications without conflicting with the provided libraries in the runtime. Again, using the last version available is the recommended way to go. Mule 3 applications are not compatible with Mule 4, so you will need to migrate existing applications.
I have not been able to locate documentation indicating whether Windows 10 IoT Core supports WFP in any capacity. I am particularly interested in whether IoT Core supports WFP callout drivers.
Background on WFP
You may try to run the WFP sample on Windows IoT Core. It includes a driver project named WFPSamplerCalloutDriver. Since the the target of projectis for Windows Desktop, it may show error when compiling for Windows IoT Core. You need to change the DriverTargetPlatform to Universal which supports Windows IoT Core.
Windows Filtering Platform Sample
Update:
I have compiled the WFPSamplerCalloutDriver sample for Windows IoT Core successfully, and built/installed the driver package on my device(Raspberry PI) with no errors. But I can not find the installed drivers via command devcon driverfiles * after booting the device.
I have to use Restheart APIs in an OpenShift application.
I tried to execute restheart.jar as suggested in the installation and use guide, but it produced an error, due to the difference between the installed java version (openjdk 7) and the required one (oracle java 8).
Is there any trick to get Restheart APIs working in an OpenShift app?
OpenShift does not support JDK 8 but that doesn’t mean you can’t run Java 8 applications.
You can use a DIY cartridge and install your own JDK version.
I am newbie with WebSphere. Recently I downloaded WebSphere Community Edition version 3 (WASCE v3) but there is no description about using WASCE v3 with JSF2.0 in the guide "Getting started with WASCE". I already build my web in Apache Tomcat 7.0.11 with JSF2.0 and PrimeFaces 3.1. I am using eclipse INDIGO. Now i have to shift my server to WebSphere. Please suggest me the best version of WebSphere, which is suitable for JSF2.0 with PrimeFaces3.1?
Thank you.
WASCE 3 is a Java EE 6 container, so it has support for JSF 2.0 (if it wouldn't have this, it couldn't be called Java EE 6).
Do note that people typically don't mean WASCE when they refer to WebSphere. WASCE is another name for the server otherwise known as Apache Geronimo. The difference is that it's specifically supported by IBM.
What people do mean with WebSphere is the one you can find here: ibm.com/software/webservers/appserv/was
For JSF 2.0 you would need the latest version, which is version 8.