I am upgrading openwebbeans project from openJDK12 to OpenJDK17 . currently webeans version is being used 2.0.10 . When upgrading application is not coming up. Is there any apachewebbeans version supporting java 17 and in near future any plan?
UPDATE: OWB-2.0.27 is compatible to JDK17 without having to change the xbean- libraries.
According to this site (https://openwebbeans.apache.org/download.html) OWB-2.0.x should support Java17.
It uses a shaded version of ASM-9 (Java17 support) for building our proxies and requires JavaSE 8 as minimum version.
But i have also problems getting the OWB-2.0.26 version to run with JDK17 because of the used xbean-asm9-shaded lib which only supports java up to version 16.
Related
My project uses .NET Standard Library version 2.1.0. One of the packages that it references is System.Net.WebSockets.Client version 4.0.2.0. This package in its turn has a dependency on System.Security.Cryptography.X509Certificates version 4.1.0. As a result, when I restore before build, this particular version gets downloaded. The issue is version 4.1.0 of System.Security.Cryptography.X509Certificates has a known vulnerability and should get updated to 4.1.2 which has the vulnerability fixed.
I am not sure how to update the version of a package that is being internally referenced from another package which itself is part of the .NET Standard Library.
I am getting flagged in my build for using the non-compliant version of the X509Cerificates package. Any pointers in this regard would be much appreciated.
Thanks.
I would like to have the procedure to compile iText 5.5.x using Javac 1.3.1.
We have a old application that can perform java calls but it is only certified with Java 1.3.1.
Note that I'm novice to java, so a step by step would be nice.
Thanks.
We are currently using JasperReports Library 4.4.7 with JDK 1.6_23 on SAP NetWeaver 7.3 and we are planing to upgrade to 5.5.2, is it compatible with our environment JDK (1.6_23) since the library is compiled using JDK 1.7 ?
If the library is compiled using JDK 1.7, it won't run on Java SE 6-compatible environment. You would need to compile it (and jar) yourself -- I don't know the library, but it's likely to fail. Perhaps they switched to Java 7 compilation to use Java 7 features.
You may also "downgrade" the compiled byte code of the library to be Java 6 compliant -- see Compiling Java 7 to Java 6 (I have no experience with that either).
I'm using FDT 3 enterprise with Flex 4.5 SDK on Mac OSX
Running works fine.
Debugging throws an internal error:
java.lang.NullPointerException
at com.powerflasher.fdt.core.launch.debug.concrete.FDBVersionTools.versionParts(FDBVersionTools.java:44)
at com.powerflasher.fdt.core.launch.debug.concrete.FDBVersionTools.compare(FDBVersionTools.java:19)
at com.powerflasher.fdt.core.launch.debug.concrete.FDBVersionTools.lessOrEqual(FDBVersionTools.java:7)
at com.powerflasher.fdt.core.launch.debug.concrete.FDBVersionTools.inRange(FDBVersionTools.java:54)
at com.powerflasher.fdt.internal.core.debugger.adapter.FlexSdkVersionTools.covers(FlexSdkVersionTools.java:25)
at com.powerflasher.fdt.internal.core.debugger.adapter.FDBAdapterLoader.cover(FDBAdapterLoader.java:51)
at com.powerflasher.fdt.internal.core.debugger.adapter.FlexDebuggerLoader.searchAdapterLoader(FlexDebuggerLoader.java:88)
at com.powerflasher.fdt.internal.core.debugger.adapter.FlexDebuggerLoader.loadDebugger(FlexDebuggerLoader.java:81)
at com.powerflasher.fdt.core.launch.DebugSessionManager.getDebuggerFor(DebugSessionManager.java:50)
at com.powerflasher.fdt.core.launch.DebugSessionManager.launchSessionFor(DebugSessionManager.java:106)
at com.powerflasher.fdt.core.launch.DebugSessionManager.launchSessionAndKillOld(DebugSessionManager.java:146)
at com.powerflasher.fdt.ui.launch.StartDebuggerTestLaunchConfigurationDelegate.startDebugger(StartDebuggerTestLaunchConfigurationDelegate.java:36)
at com.powerflasher.fdt.internal.ui.launch.fcsh.MxmlcLaunchConfigurationDelegate.startDebugger(MxmlcLaunchConfigurationDelegate.java:348)
at com.powerflasher.fdt.internal.ui.launch.fcsh.AbstractFCSHLaunchConfigurationDelegate.launch(AbstractFCSHLaunchConfigurationDelegate.java:174)
at com.powerflasher.fdt.internal.ui.launch.fcsh.MxmlcLaunchConfigurationDelegate.launch(MxmlcLaunchConfigurationDelegate.java:237)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:866)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1069)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
I'm not using any uncommon debug/compiler-arguments
Has anyone seen this before?
The Flex Debugger API changed quite a bit from Flex 3.X - 4.0. This means that your older FDT (version 3.x) is likely not compatible with later Flex SDKs. That is why you are getting that error.
You'll need to upgrade to 5.5 (or FDT 4.5 if you have a FDT 4 license)b/c the FDT team has had to rewrite parts of the debugger to make it compatible with Flex 4.5+. We've done our best to keep the upgrade price minimal.
http://fdt.powerflasher.com/buy-download/
I recently added a static library (mobclix) to my iPhone project which required me to set the Base SDK to 3.0. This library is claimed to be compatible with 2.2 and so far it looks like it's true. I set the project's Deployment Target to 2.2. No problems there.
Now, I am also using libxml2 in this same project. Apparently, the libxml2.2.dylib in OS 3.0 is newer than in OS 2.X (version 10 and 9 respectively). However, my code that uses libxml2, was already compatible with the libxml2 version included with OS 2.X. Since I needed to set the Base SDK to 3.0, the "compatibility version" / minimum version requirement / dependency is automatically set to the newer version of libxml2. When I try to run the app in OS 2, I get this runtime error (obviously):
Dyld Error Message:
Library not loaded: /usr/lib/libxml2.2.dylib
Referenced from: /Users/Martijn/Library/Application Support/iPhone Simulator/User/Applications/4D5456DE-F297-4DF4-ACA6-DA8BBBBBA914/Luisterpaal.app/Luisterpaal
Reason: Incompatible library version: Luisterpaal requires version 10.0.0 or later, but libxml2.2.dylib provides version 9.0.0
Is it possible to override the version requirement somewhere?
Or other ideas to solve this issue?
The compatibility version is set according to the version embedded in the dylib of the current SDK during build. I have not found a way to change or override this.
However, in the target in Xcode under the "Link with binary with libraries" branch there is an option to link a dylib "weakly". This skips version checking at the time of loading the dylib (runtime). It's your responsibility then to only make calls to existing functions. Making calls to non-existent functions will crash the application.
Apparently there was a change with SDK 3.0 that broke compatibility with libxml. Apple have posted about it here:
http://developer.apple.com/iphone/library/qa/qa2009/qa1659.html