For all JSF folks out there. Some important news happened. What is it? Well, Ed Burns announced Oracle's intent to file JSF 2.3 JSR with me as co-spec lead. See the email to the EG at https://java.net/projects/javaserverfaces-spec-public/lists/users/archiv...
In JSF you will see people from time to time use rendered="false". But what does it mean?
Well, because in JSF the actual request is page based it builds up a representation of the page when the page gets loaded. When it is building up this representation it builds up the entire page, even the parts that are not going to be rendered.
If you like to automate things you might wonder if it is possible to create a Weblogic domain using Maven? Indeed that is possible. See the steps below!
- Install the Maven plugin
- Create the Weblogic domain
1. Install the Maven plugin
Just in case you missed it, see https://blogs.oracle.com/theaquarium/entry/glassfish_4_0_1_update for a roadmap for Glassfish 4.0.1
Have you ever wondered if it is possible to install Oracle Weblogic Server using Maven? Well, it is.
- Install the Weblogic plugin
- Use the Weblogic plugin
1. Install the Weblogic plugin
Here is a bit of a chicken and the egg story. You will have to have an existing Weblogic install to
If you want to determine the size of the response buffer the JSF runtime uses when buffering then the 'com.sun.faces.responseBufferSize' context-param allows you to set the size to something you want. The default is 1024 bytes, which is not big, but also not too large.
See the example snippet below which you could put in your faces-config.xml.
Hurray Java 8 is out! See for more information at http://www.oracle.com/technetwork/java/javase/overview/java8-2100321.html
In every JSF application view state is kept either on the client or on the server. How do you make sure this state is smaller?
Today we are covering what the "com.sun.faces.sendPoweredByHeader" context-param does.
The "com.sun.faces.validateXml" context-param makes it possible for you to have the Mojarra JSF runtime verify your configuration files against the faces-config.xml schema. If an error is found you will immediately be made aware as deployment will fail until you fix the problem.