Development

Using form based authentication in JSF always makes me look for a login form that uses h:form instead of plain html. Here is a form that uses JAAS with proper xhtml using the JSF h:form tag: <h:form id=”login” onsubmit=”document.getElementById(‘login’).action=’j_security_check’;” prependId=”false”> <h:outputLabel for=”j_username” value=”Username:” /> <h:inputText id=”j_username” size=”32″ /> <h:outputLabel for=”j_password” value=”Password:” /> <h:inputSecret id=”j_password” size=”255″ […]

In my glassfish4 I got the following log messages that a certificate has expired: Severe: SEC5054: Certificate has expired: [ [ Version: V3 Subject: CN=GTE CyberTrust Root 5, OU=”GTE CyberTrust Solutions, Inc.”, O=GTE Corporation, C=US Signature Algorithm: SHA1withRSA, “”OID”” = 1.2.840.113549.1.1.5 Key: Sun RSA public key, 2048 bits … Here is how to remove this

Under Eclipse Luna (4.4) M6 my JSF project gave exceptions like the following when I had EL snipplets like <h:commandButton action=”#{userController.delete(u)}” … And here the error in eclipse: Method must have signature “String method(), String method(), String method(String), String method(String, String), String method(String, String, String), String method(String, String, String, String), String method(String, String, String, String,

I found a strange behavior in JSF 2.2: When using the new jcp namespaces for ui:repeat it renders something like this: <ul> <ui:repeat><li>a</li></ui:repeat> <ui:repeat><li>b</li></ui:repeat> <ui:repeat><li>c</li></ui:repeat> </ul> To get rid of this I went back to the old java.sun.com/jsf urls in the whole project and everything was working as expected. Here is how I was able to

As the latest trunk of wordpress broke my blog I had to switch to the latest tag and was looking for a way to do that without checking out a new directory and changing my configuration and so on. See information about the actual working directory: svn info Switch to another tag or branch (or

Security manager installed using the Basic server security policy. access denied (“java.net.SocketPermission””localhost:1527″”listen,resolve”) Java 7u51 contains changes in the security manager. It was allowed to use ports >1024. Now this port range was moved much higher. To be able to use lower ports there has to be a line in java.policy which is located in $JAVA_HOME/jre/lib/security Here

Just add the following to your _tomee_/conf/tomee.xml file to get a hsqldb datasource with an in memory datasource which you can use as jta-datasource named exampleDS: <Resource id=”exampleDS” type=”DataSource”> JdbcDriver org.hsqldb.jdbcDriver JdbcUrl jdbc:hsqldb:mem:exampledb;DB_CLOSE_DELAY=-1; UserName sa Password JtaManaged true </Resource>

Because TomEE comes with a java.util.Logging Logger which I really dislike, I decided to change the logger to log4j through slf4j. Here are the steps to achieve this: Create a folder _tomee_/bin/log and place the following libraries in it: jul-to-slf4j-1.7.5.jar, log4j-1.2.17.jar, slf4j-api-1.7.5.jar, slf4j-log4j12-1.7.5.jar Remove slf4j-*jdk*.jar and slf4j-*api*.jar from _tomee_/lib Create a log4j.properties file in _tomee_/bin/log/config Create a file named setenv.sh in _tomee_/bin