PF 11.0.0: which mojarra versions are supported?
It is not specified in pom.xml. The showcase used to show the mojarra version, but not now.
Based on documentation PrimeFaces 11 has dependency JSF with ver. 2.0, 2.1, 2.2, 2.3, 3.0, 4.0. Where JSF can be Apache MyFaces or Eclipse (former Oracle) Mojarra.
Related
/build/Debug/ant/pdm.jar!/META-INF/versions/9/org/apache/logging/log4j/util/Base64Util.class: Class Version Error. Please recompile with a supported JDK or check for an update to DashO which supports the new version.
We are using ant as build tool and Dasho as the code trimming tool.
We are migrating our code from log4j1.x to log4j2.x and we replaced old jar with new Jars(2.xapi & 2.xcore)
Since then after adding the libraries itself we are getting this error while building the project,as we are using java 8 and as per official log4j2 documentation any version of lof4j2 above 2.17.1 does support java8
Found this line when searched for this Base64Util.class in the official documentation of 2.x
link
Tried using 2.17.1 && 2.15 && 2.13 but no luck
Why this unsupported JDK is coming even after using java8 in project??
In order to support Java 8 and all later releases the log4j-api and log4j-core artifacts are multi-release jars. The class file that gives you problems uses Java 9 bytecode.
According to their web site DashO does not support multi-release jars.
Remark: removing the Java 9 classes from log4j-api and log4j-core will break logger context selection and location information on JDK 9 and later, so it is not an option.
Recently we have migrated from Mojarra 2.2.15 to myfaces 2.2.11 version and found that Primefaces Lifecycle component is not working.
Note: We are using Wildfly 11
we have added following content in faces-config.xml
<lifecycle>
<phase-listener>org.primefaces.component.lifecycle.LifecyclePhaseListener</phase-listener>
</lifecycle>
Above configuration for p:lifecycle works fine with Mojarra but same is not working with Myfaces. How to solve this issue.
I am working on web application with JSF and I try to make notifications by Primefaces Push but when I run the project I got this exception :
java.lang.NoSuchFieldError: framework
at org.primefaces.push.PushServlet.configureFramework(PushServlet.java:66)
at org.primefaces.push.PushServlet.configureFramework(PushServlet.java:36)
at org.atmosphere.cpr.AtmosphereServlet.init(AtmosphereServlet.java:74)
Also I added this Libraries :
primefaces 5.0 atmosphere-runtime-2.3.5 slf4j-api-1.7.7 commons-lang3-3.4
You should use an Atmosphere version that is compatible with PrimeFaces 5.0. That is 2.1.3 according to the docs, pom and releasenotes.
We have an javaee application already running on Wildfly 8.1 and we want to migrate it on JBoss EAP 6 because our customer needs a commercial license.
On Wildfly we have the following configuration
<subsystem xmlns="urn:jboss:domain:ee:1.2">
...
<concurrent>
<context-services>
<context-service name="default" jndi-name="java:jboss/ee/concurrency/context/default" use-transaction-setup-provider="true"/>
</context-services>
<managed-thread-factories>
<managed-thread-factory name="default" jndi-name="java:jboss/ee/concurrency/factory/default" context-service="default"/>
</managed-thread-factories>
<managed-executor-services>
<managed-executor-service name="default" jndi-name="java:jboss/ee/concurrency/executor/default" context-service="default" hung-task-threshold="60000" core-threads="50" max-threads="500" keepalive-time="5000" queue-length="1000"/>
</managed-executor-services>
<managed-scheduled-executor-services>
<managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" hung-task-threshold="60000" core-threads="2" keepalive-time="3000"/>
</managed-scheduled-executor-services>
</concurrent>
<default-bindings context-service="java:jboss/ee/concurrency/context/default" jms-connection-factory="java:jboss/DefaultJMSConnectionFactory" managed-executor-service="java:jboss/ee/concurrency/executor/default" managed-scheduled-executor-service="java:jboss/ee/concurrency/scheduler/default" managed-thread-factory="java:jboss/ee/concurrency/factory/default"/>
How could we configure it on JBoss EAP? We read the documentation but the "concurrent" tag does not exist and we want to manage the concurrent threads.
Wildfly 8 was the first version towards a Java EE 7 compliant application server. Wildfly 10 is the latest version in that line.
JBoss EAP 7 is the supported version corresponding to WildFly 10. It is now in Beta.
So in short if you want to use the concurrent tag then you need to use JBoss EAP 7.
You're actually downgrading. JBoss EAP 6.2 is based on JBoss Application Server (AS) 7.3.0.Final. See the JBoss EAP component matrix for reference.
As you can see, EAP 7 is not there, as it was not released yet. The page is being updated as the component versions settle. Once it's out there, instead of JBoss AS, there will be WildFly. For EAP 7, it will be WildFly 10.x, as ozOli wrote.
JBoss EAP 7 (not sure about WildFly 10) has a feature which takes your old standalone.xml and converts it to the new configuration - namespaces, subsystems.
Once there was a tool under development called WindRide which aimed at automated configuration migration, but that was cutted off few years back.
In addition to automated server configuration migration, there are tools to assist with automated application migration:
JBoss Windup - pluggable customizable rule-based automated migration tool.
Pretty good*.
*) reference: me - I'm one of developers :)
When I try to build the JDBC driver, from the source downloaded from here , I get many compilation errors. For example,
The type CallableStatement must implement the inherited abstract method CallableStatement.getCharacterStream(int)
in CallableStatement.java line 57
All these error indicate, I thought, that the driver is compatible with JDK 1.5, because the specified method wasn't part of the JDBC spec in JDK 1.5.
However, when I tried to build the driver with JDK 1.5, I got errors indicating that JDK 1.6 is required. For example,
The import java.sql.RowIdLifetime cannot be resolved
where RowIdLifetime is a class that wasn't part of JDK 1.5.
So, which one is it? JDK 1.5 or 1.6? Am I missing something when I try to build?
Having read the file connector-j.html that is bundled with the source, it looks like I need both:
If you are building Connector/J 5.1 make sure that you have both JDK 1.6.x installed and an older JDK such as JDK 1.5.x. This is because Connector/J supports both JDBC 3.0 (which was prior to JDK 1.6.x) and JDBC 4.0. Set your JAVA_HOME environment variable to the path of the older JDK installation.
Next time, I'll RTM before posting.