Set the warnLogCategory attribute to log uncaught exception stacktrace: <bean class="org.springframework.web.servl...

Lacking better alternatives, this is how I render a global validation error: <spring:bind path="changePasswordForm"> <c:if ... <form:errors> without path attribute seems to work too: <form:errors cssClass="ui-error"/>

1. pom.xml <plugin> <groupId>org.jvnet.jax-ws-commons<... 2. To ignore SSL cert errors: <configuration> <args> <arg>... 3. To resolve class name conflict ("Use a class customization to resolve this conflict" error): <configuration> <args> <arg>-B-Xaut...

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="$...

If forgotPasswordForm.error is a String and not null, you cannot test the error condition with: <!-- This does not work! --> <c:if test="${forg... You have to use "not empty": <c:if test="${not empty forgotPasswordForm.error}"...

Mapping Java objects to Jackson JSON is pretty simple. But if you name a JSON field wrong, you'll get the "Unrecognized field ... (Class ...), not marked as ignorable" error. The rule for mapping a Java bean attribute name to a JSON field name is: lower all leading capital letters until the first lower case letter . For example, this Java class: package com.example; public class Person { ... maps to this JSON string: { "firstName": "Jane", "lastName": "... Test code: package com.example; import java.net.URL; ...

I got this error while using Hibernate 3.5.6: org.hibernate.MappingException: An AnnotationConfi... where I used annotations for mapping in the ExampleEntity class. Problem : I initialized the session factory with Configuration : sessionFactory = new Configuration() .co... Solution : should use AnnotationConfiguration instead: sessionFactory = new AnnotationConfiguration() ... Additional Note: Hibernate 4.1 didn't seem to mind ( Configuration worked fine).

Maven is a powerful yet complex tool. When I started learning Maven, the first obstacle was, of course, its complexity. The second, was the lack of documentation that can get me off the ground quickly. This tutorial is an attempt to create a pragmatic guide that aims to get you familiar with Maven in the quickest way possible. The main theme is to get you on some hands on experience to start out and lead you through the creation of a simple Java EE project as quickly as possible. Instead of trying to give you a good read, I try to get you on the journey right away. The topics are roughly ordered by the logical sequence but you can jump around in any way...

The domain object is annotated @Entity , but Java runtime complains that it's not an entity class. Cause: : class not listed in persistence.xml , or persistence.xml misplaced, or multiple persistence.xml files existed.

Tomcat 7.0 failed with a SEVERE error without printing a stack trace: Dec 30, 2011 1:21:09 PM org.apache.catalina.core.S... Now it's hard to figure out what's wrong without knowing where things went wrong. Why is Tomcat not logging anything? Tomcat logging is configured by class loader. Logging behaves differently depending on which class loader loaded the logger. You'll need to look at both $CATALINA_BASE/conf/logging.properties and WEB-INF/classes/logging.properties to figure out why the stack trace is not logged. In my case, the web app specific WEB-INF/classes/logging.properties overshadowed the system $CATALINA_BASE/conf/logging.properties and suppressed the stack trace.