3 Replies Latest reply on Nov 12, 2007 2:29 PM by delphi'sghost

    Overzealous Validation of Object

    delphi'sghost

      I have an abstract class that I was going to use as the base for some Seam EJB components.

      Since every stateful Seam EJB Component needs a @destroy annotated method, I thought I'd put that in the base class. EntityHome does this with the @Create annotated method

      However, since the abstract class itself is not a Seam component, then the IDE complains that only Seam components can have a @Destroy annotated method in them, which in all fairness is quite true.

      Any chance the validator can be loosened up to ignore that issue if the class is abstract?

      This is of course assuming that a @Destroy annotated method in a parent class will do the job. I'm assuming it will because a @Create annotated method works when used in the EntityHome objects which I subclass.