JEE6 - @ApplicationException - @Inject and @PostConstruct not called

[kernstock]

Hi,

I have a problem with @Inject and @PostConstruct method not called in a @ApplicationException annoted class. I'm using Glassfish 3.0.1 with JPA,CDI and EJBs in the service(ejb)-layer and would like to throw an errorMessage that contains a text in the sessionlanguage.

I have an abstract ExceptionClass

     public abstract class LocalizedException extends Exception {
            private static final long serialVersionUID = 1L;
    
     @Inject 
     protected LocaleHandler locHandler;
     
     String localizedMessage;
     
            //This method should be called as @PostConstruct from the concrete classe
     protected void setLocalizedMessage(String key){
      this.setLocalizedMessage(key, new Object());
     }
     
     protected void setLocalizedMessage(String key, Object... args){
      localizedMessage = ErrorMessages.getErrorMessage(key,locHandler.getCurrentLocale(),args);
     }
     
     @Override
     public String getMessage() {
      return localizedMessage;
     }
    
     @Override
     public String getLocalizedMessage() {
      return localizedMessage;
     }
   }

And a concrete class:

  @ApplicationException
  public class ConcreteException extends LocalizedException {
     private static final long serialVersionUID = 2615388267911318734L;
     private int userId;
    
     public ConcreteException(int userId) {
         this.userId=userId;
     }
    
     public int getUserId() {
      return userId;
     }
     
     @PostConstruct 
      public void initText(){
         setLocalizedMessage("msgKey");
      }
  }

The LocaleHandler (Sessionscoped) should be injected to provide the currentLocale which is used to retrieve an errormessage from a bundle.
The problem is, that the @PostConstruct is never called no matter what I try. I even annoted the concrete class with @Named, used @Inject in the concrete class instead of the abstract, but nothing works. When I call initText() directly I can see (in the debugger), that the LocaleHandler is not injected.

Now I'm asking myself if there is a restriction regarding Exception classes and CDI or did I simply not find the source of the problem !

Do you know the answer ?

thanx in advance

Thomas

[ranophoenix]

Do you have a file named beans.xml in your classpath? (It's basic but sometimes happens)

[kernstock]

Yes, I have. I'm using CDI all over different classes and this works correctly.

[jharting]

How do you throw the exception?

[cernicb]

In your concrete class you don't have default or @Inject constructor, so you can't inject your exception service into ejb bean or whether it's supposed to be injected. So I guess you obtain exception instance via new. Is that a reason why postconstruct is never called?

[kernstock]

@Josef and @Branislav,

thank you very much for your reply. And of course you're right - I coded  throw new ConcreteException(id) - since I'm used to do that since ages :-)

I now inject the ConcreteException into my service and throw the injected field instead and this works perfectly.

Thanx again - you saved my day.

Thomas

[kapitanpetko]

Thomas Kernstock wrote on Dec 23, 2010 12:21:


@Josef and @Branislav,


thank you very much for your reply. And of course you're right - I coded  throw new ConcreteException(id) - since I'm used to do that since ages :-)

I now inject the ConcreteException into my service and throw the injected field instead and this works perfectly.

The question now is: is it a good idea to make your exception all that smart? Exceptions are basic classes and you may get errors all over the place when logging, dumping, etc., since practically no library you use is aware of CDI, @Inject, etc. Might be a better idea to have an ExceptionFactory or whatever, that injects LocaleHandler and produces simple, dumb exception instances that have the correct message stored.

[kernstock]

Nikolay,

thank you for your post. I will think about that.

regards

Thomas