Recent Notes

Displaying keyword search results 1 - 4
Created by Fang on March 15, 2012 10:24:35    Last update: March 15, 2012 10:24:35
Suppose that I have an email field annotated with: @NotEmpty(message="Please enter email address") ... Bean validation will trigger two errors when no email address is entered: the email field is empty an empty email field is not a valid email address Displaying both errors to the user with <form:errors> would be redundant and confusing: <%@ taglib uri="http://www.springframework.org/tag... This is how to display the first error only: <spring:bind path="emailAddress"> <c:if test="$...
Created by alfa on April 06, 2011 13:13:34    Last update: April 06, 2011 13:13:34
This error happens when the class exists but it does not match the package name. In the screen capture below, the class Nothing exists but it doesn't reside in the com.demo.io package. $ java com.demo.io.Nothing Exception in thread ... A much shorter error message displays if the class does not exist at all: $ java com.demo.io.Nothing2 Exception in thread...
Created by nogeek on February 03, 2011 13:08:38    Last update: February 03, 2011 13:14:10
The log line was like this: 2011-01-19 15:16:34,842 INFO [STDOUT] (HDScanne... Note that INFO and timestamp were printed twice. Based on my configuration, I was expecting something like this: 2011-01-19 15:16:34,842 INFO [XmlWebApplicationC... i.e., the logger name should have been XmlWebApplicationContext , not STDOUT ! What was the problem? I found this error message in server.log : 2011-01-19 14:34:38,107 ERROR [STDERR] (main) lo... It turned out that org.apache.log4j.Appender was loaded by my web application class loader, whereas org.jboss.logging.appender.FileAppender was loaded by the JBoss bootstrap class loader. Removing the log4j jar from my web application archive fixed the problem (sine log4j is already available in JBoss). Why was the logger changed to STDOUT? JBoss detects that there's a problem with the log4j configuration and routes all...
Created by Dr. Xi on March 02, 2010 00:07:48    Last update: March 02, 2010 00:07:48
OC4J didn't offer much help in the console. This is all it displayed: 2010-03-01 15:48:21.372 ERROR J2EE EJB-03027 [Fab... However, in the em console, Logs -> Diagnostic Logs gives more details: Message Text [FabulousApp] An error occured deploying EJB mod... Supplemental Text com.evermind.server.ejb.exception.DeploymentExcept... The error was caused by a relationship annotation between two entities, the referenced attribute was removed from the owner side: @OneToMany(cascade=CascadeType.ALL, mapped...