upgradeable | Experiment with upgradeable contracts

You appear to be using a Linux/Unix system, based on your error: zsh: command not found: mariadb-java-client-2.7.1.jar.

Your Java command therefore needs to use a colon :, not a semicolon ;.

Semicolons are the JAR separators used on Windows for the java command. But for Linux, it is the colon (and you can see this in the usage message: A : separated list of directories, JAR archives...).

Therefore, try this:

The error message you quoted shows the cause of the problem. When the server instance was defined, the JVM launch arguments set for it included a reference to endorsed directories, an argument valid through Java 8, but not for Java 9 and newer. When you open the editor for your server instance from inside the Servers View, in the General Information section, Click on the Runtime Environment link and change the JRE explicitly to a Java 8 version. The server should then start up again.

I ran into the same problem, because the project was targeted to SQL 2019, while I am using SQL 2017. I changed it to SQL 2017 in the VS project properties and it worked!

put a dot before the class name.

Apparently this has been build also with ghc-8.6.3. Such a version of ghc is available in stack's snapshot 13.11. If you wish, change stack.yaml to set the resolver to lts-13.11. It'll download a different version of the compiler and libraries. Maybe it works

as you've said, you have to add allow-newer: true so it can resolve dependencies properly

I believe there are two things going on here. One looks like it's fatal, but might not be, and the other is definitely fatal.

The first thing you should do at the same shell prompt is run "java -version". I believe that will likely give you an error of some kind, instead of printing the version of Java you have installed and in your PATH. If this fails, then you have to properly install Java.

I believe that the message about JAVA_HOME not being set is a red herring. If I remember correctly, Karaf incorrectly complains about this. I believe it will work perfectly fine if Java is properly installed and in your PATH.

The endorsed directories have been removed since Java 9. So the error message suggests that you are running with at least Java 9.

You need to use Java 8 for this to work. If I remember correctly then Glassfish does not support Java 9 and higher.

You're describing a type-reasoning feature called covariance, which is itself a consequence of the Liskov Substitution Principle.

As of PHP 7.4, this works as you expect. (See the RFC implementing the behavior for details.)

Prior to then, this was discussed on internals. As was stated in one such conversation:

if an implementation better than satisfies the requirements defined by an interface, it should be able to implement that interface.

So, yes, PHP should allow covariance as you describe. But realize: it's not that PHP refuses to implement covariance, it's that PHP has not yet implemented covariance. There are some technical hurdles to doing so, but they're not insurmountable. As was stated in that same thread on internals by a core maintainer:

It's doable, it just hasn't been done.

If you'd like to produce an RFC and a PR, please do so. Until then, it's just an unfortunate status quo of the ever-evolving PHP object system.

I got the Apache CXF 3.3.1 wsdl2java utility to work with the latest OpenJDK 11 by doing 4 things:

1. Pull down this jar and place it into the {CXF_HOME}/lib directory: https://mvnrepository.com/artifact/javax.jws/jsr181-api/1.0-MR1
2. Pull down this jar and also place it in the {CXF_HOME}/lib directory: https://mvnrepository.com/artifact/javax.xml.ws/jaxws-api/2.3.1

3. In my case, since I'm running on a Mac, I vi'd the wsdl2java script and made sure these two jars are explicitly being set on the CXF classpath, by doing the following declaration within the script right before the execution of the java command:cxf_classpath=${cxf_classpath}:../lib/jaxws-api-2.3.1.jar:../lib/jsr181-api-1.0-MR1.jar

4. Lastly, I removed the '-Djava.endorsed.dirs="${cxf_home}/lib/endorsed"' parameter from the java command at the end of the script, since newer JDKs no longer support this argument, so my command now looks like this:$JAVA_HOME/bin/java -Xmx${JAVA_MAX_MEM} -cp "${cxf_classpath}" -Djava.util.logging.config.file=$log_config org.apache.cxf.tools.wsdlto.WSDLToJava "$@"

Now, using OpenJDK11, I'm able to point to an external WSDL file and successfully generate the client code I need to consume this SOAP service with the following command: