The method destroy is called twice

[deved]

Hi all. I have this:
TableModel.java

@Name("tableModel")
@Conversational
@Scope(ScopeType.CONVERSATION)
public class TableModel {

 @In
 private EntityManager em;

 private List data;

 @Begin
 public void begin(Class entityClass) {
 data = query(entityClass);
 }

 @Destroy
 public void clean() {
 data.clear();
 data = null;
 }

 public List getData() {
 return data;
 }

 private List query(Class entityClass) {
 ....
 }
}

MenuManager.java

@Name("menuManager")
@Scope(ScopeType.SESSION)
public class MenuManager{

 private TableModel tableModel;

 public String redirect() {
 if(tableModel != null) {
 tableModel.clean();
 }
 tableModel = (TableModel) Component.getInstance("tableModel", ScopeType.CONVERSATION);
 tabelModel.begin(SomeEntity.class);
 }
}

When I call "tableModel.clean()" the field "data" on TableModel is null.
Then when the session is ended or the conversation timeout expire the method is called again, this is right?
Any help, thanks.

[norman.richards]

Are you saying that you think that the destroy callback shouldn't be called if you have already manually called it?

[deved]

Yes. I am wrong? Why should be called more than once?

[norman.richards]

The destroy callback is always called by Seam. It doesn't know (or care) if you have called this method yourself.

[monkeyden]

If you want Seam to call it twice, just use this @BeatADeadHorse annotation.

Note: No actual horses, dead or alive, are harmed by this annotation

[deved]

Hi Richards. I try with "tableModel.clean()" and with this:

if(tableModel !=null) {
Component component = Seam.componentForName("tableModel");
component.destroy(tableModel);
//component.callDestroyMethod(tableModel);
}

And I have the same result.
When I call @Destroy method this way, Seam doesn't know?
What difference exist between "component.destroy" and "component.callDestroyMethod"?
I can't manually call @Destroy, when I know exactly when should be called?

Thanks Richards.