Depends on how user gets to this bean, if it's from edit page code, Seam will reset the field to null even if you have field initialization. 

Patrick Huang 
Senior Software Engineer 
Engineering - Internationalisation 
Red Hat 

----- Original Message -----

> From: "Sean Flanigan" <notifications@github.com>
> To: "zanata/zanata-server" <zanata-server@noreply.github.com>
> Cc: "Patrick Huang" <pahuang@redhat.com>
> Sent: Thursday, November 14, 2013 3:21:56 PM
> Subject: Re: [zanata-server] rhbz1026155 - fix NPE (#270)

> In zanata-war/src/main/java/org/zanata/action/ProjectHome.java:
> > @@ -309,10 +291,13 @@ private void updateOverrideLocales() {
> >      }
> >
> >      private void updateOverrideValidations() {
> > -        getInstance().getCustomizedValidations().clear();
> > -        for (ValidationAction action : customizedValidations) {
> > -
> >            getInstance().getCustomizedValidations().put(action.getId().name(),
> > -                    action.getState().name());
> > +        // edit project page code won't have customized validations
> > outjected
> > +        if (customizedValidations != null) {

> Instead of needing a null check, could we ensure that customizedValidations
> is always non-null, but empty if necessary?

> —
> Reply to this email directly or view it on GitHub .