How to debug the root cause for AssertionFailure: null id in entry (don't flush the Session after an exception occurs)

To figure out the real (root) cause of the error, please use the following snippet

     ClassValidator cv = new ClassValidator(YourEntity.class);
                    InvalidValue[] validationMessages = cv.getInvalidValues(yourInstanceOfEntity);
                    if (validationMessages.length > 0) {
                        for (InvalidValue iv : validationMessages) {
                            System.out.println("Invalid value::" +iv.getMessage()+"::"+iv.getPropertyName()+"::"+iv.getValue());
                        }
                    }

Migration from Seam 2 to Seam 3

I am migrating one of my application from Seam 2 to Seam 3 and hence posting my observations in this post. The post is not complete yet and i will be adding to it when ever i work on the migration.

1.  To begin with configure the profile mentioned in this link either in your pom.xml or settings.xml. Else the build will fail to resolve parent pom.
2. Install Maven 3.0.3 or above. Certain Maven plugins will not work with 2.2.1 or any 2.x.x versions.
 

UPDATE: As Seam 3.0 is lacking many of the features in Seam 2.0 I have paused the migration as of now and waiting for Seam 3.1 release

 

Generating a self signed certificate specifying validity using keytool in JDK

Sometimes you may wish to change the default validity of a JDK keytool generated self signed certificate in your development environment. Use the argument validity to control the validity period. In the below example the validity is 10 years.

keytool -genkey -keystore yourname.keys -alias somealias -validity 3650