This content has been marked as final. Show 2 replies
The validor is partially right, as these class doesn't have these methods, but they are inherited: I think the validator should look also on annotations of superclasses.
Yes, you are rigth. This is a bug. Please, submit it to JIRA.
A second problem I have with the same validator is
Duplicate @Remove method "methodname"
even on standard beans (non-entity). The configuration panel for the validator has a section to control this, but looks to be only for entities. This is not an entity, still I can disable it there as a workaround.
And there is another bug :) The validator should check duplicate @Remove method only for stateful session bean component. Please, submit it to JIRA too.
I didn't know I couldn't have multiple @Remove on an entity, is that true?
At least Seam does not allow to have multiple @Remove in stateful session bean components.
If you try then Seam throws IllegalArgumentException("Stateful session bean component must have a method with no parameters marked @Remove: " + name);