Arquillian meets JRebel

Writing tests with Arquillian is so cool. Our tests are run in container, we can inject various artifacts like EJBs, JMS queues, CDI beans and more into our tests.
But the turnaround for big deployments is too big. Even for smaller ones, if you for example use Seam3 or Hibernate it takes some seconds to redeploy. And those seconds add up.

But I've got good news for you!

AS7 Seam2 LoggingFilter

Seam2 allows us to add user name to each server log entry triggered by that user. This is described id "Identity Logging" chapter. We only need to enable logging-filter in components.xml and add %X{username} to log pattern.

But what if we want more, like IP ?

Mock contexts for Arquillian

Do you have @ViewScoped or @ConversationScoped annotated beans that you want to test with Arquillian?

Do you get "WELD-001303 No active contexts for scope type javax.enterprise.context.ConversationScoped"?

Well now you get mock-contexts-extension to the rescue.

CDK Guide - Writing schedule component

The goal

There is a lot of good introductory tutorials on writing JSF components based on RichFaces and using CDK. However they cover very simple cases and developers have hard times figuring out how to tackle some more advanced scenarios which are easily achievable in RichFaces.

Seam3-persistence-framework comes to town

Seam2 had great "framework-in-framework" set of classes to speed up CRUD development. I'm talking about EntityHome and EntityQuery. If you miss that stuff a lot in Seam3, don't you worry, cause IT Crowd has migrated EntityHomes and such successfully to seam3 and we use it in production.