In ADF, you can easily add method validators on Entity level. However, sometimes this is not enough. If your validation logic is complex (for instance: if you need all other rows to validate against, for some kind of special uniqueness constraint), this is not enough.
You can throw a general exception from the setter of your attribute in the view object, but that is not enough, because this will look different (no 'red' field, and a different style of exception on the screen).
General method in the view row base class.
After killing the eclipse process and restarting my pc, Eclipse was not able to startup anymore.
org.eclipse.core.internal.dtree.ObjectNotFoundException: Tree element 'mypckg/myClass.class' not found.
and a <p:editor>, which is an input component with rich text formatting capabilities.
But the two didn't really match. If one uses a <p:inplace> wrapped around a <p:editor>, the editor does not work as it is supposed to. The problem is that the editor is not designed to work in a container which is initially hidden. And that's just the behavior you depend on when you want to use an inplace component.
In Seam 2, if you wanted a seam component to be initialized when the application was started up, you could use the @Startup annotation.
However, this means you will need such a method for every bean, which is a lot more of overhead than the simple @Startup annotation.
First, you will need an interface. This interface does not require any methods.
The BeanStartupHelper is actually also a bean, and as you can see, this bean contains a method which observes the initialization of the webapplication. A reference to the BeanManager object is injected as a parameter of this method. We use the BeanManager object to create the beans we need, which are all beans which implement the Startup annotation.
There is a clear separation between the beans themselves and the implementation of the startup method. The only thing needed for your beans is the fact that they need to implement a Startup interface. You only need one method which observes the initialization of your application, in which all 'startup' beans will be initialized!