Skip to main content

JSF View Parameter And Java EE 7 XML namespaces


After spending several hours trying to figure out why my old sample codes won't run on Glassfish 4.0 and Java EE 7, I found out that the problem was actually with the new XML schemas for Java.

You can find more information about the new XML schemas for Java EE deployment descriptors on Oracle's website. You can also find more information about GlassFish Server Documentation on GitHub Pages.


I figured out that the problem was actually with the XML Schemas below which I had to update back to the old version.

xmlns="http://www.w3.org/1999/xhtml"
xmlns:h="http://xmlns.jcp.org/jsf/html" 
xmlns:ui="http://xmlns.jcp.org/jsf/facelets" 
xmlns:f="http://xmlns.jcp.org/jsf/core"



Working Version

xmlns="http://www.w3.org/1999/xhtml" 
xmlns:h="http://java.sun.com/jsf/html"
xmlns:p="http://primefaces.org/ui" 
xmlns:f="http://java.sun.com/jsf/core"

I receive a response from this site, which answered why the situation was like that and provided another solution.

Comments

Post a Comment

Popular posts from this blog

Fix HTTP error code 513 on Wildfly

Description :  Many users have reported a network issue where they see a large number of connections in TIME_WAIT and IDLE states. This indicates that the connections are not being closed properly by the server or the client.  When I analyzed the network traffic, I found that the server was sending HTTP Error 513 to the client, which means that the server is overloaded and cannot handle more requests. The client was also logging a socket close event, which means that the client was terminating the connection. This can be simulated using Jmeter. The HTTP error code 153 resulted from the max concurrent connection limit reached, and the allowed queue was also full. This issue can cause performance degradation and resource wastage on both the server and the client. To resolve this issue, we recommend the following steps: Resolution :  1. Investigate the process of holding onto the connection longer than necessary. 2. Increase the server capacity or scale up the server to handle mo
Post a Comment
Read more

Wildfly EJB Remote Client Exceptions.......

Below are exceptions and the solutions I applied while developing a remote client enterprise application. To start with, enable debug for your application server to see the detail and good luck troubleshooting. Exceptions : Starting with  java.lang.ClassNotFoundException: org.hibernate.collection.internal.Persistent......... Solution : I fixed the exception be adding hibernate Entity Manager Dependencies. Exception: Error javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:  java.naming.factory.initial Solution : Add JBOSS-CLIENT Dependencies to your project Exception : IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling Solution : Confirm that your EJB module have been deployed. Exception : org.jboss.naming.remote.client.initialcontextfactory wildfly     javax.naming.NamingException: WFLYNAM0027: Failed instantiate Initia
Post a Comment
Read more