Why do we need Interfaces

amarinis Mar 17, 2006 9:14 PM

OK This may sound silly but:

Following in the footsteps of seam, simplifying web based applications, I am having trouble trying to understand why an Interface is needed for every stateful action class i create.

Can someone help explain this to me. I know I am going to be asked this question by developers soon

1. Re: Why do we need Interfaces

pgmjsd Mar 20, 2006 7:35 AM (in response to amarinis)

If your 'stateful actions' are EJBs, then that's why.
Actions
2. Re: Why do we need Interfaces

gavin.king Mar 20, 2006 8:21 AM (in response to amarinis)

Yes, we discussed this in the EJB EG and at the time we decided that we wouldn't try to eliminate the requirement for interfaces. I now regret that, esp. since in the context of Seam you find yourself writing interfaces that are never actually used anywhere (the only client is the EL, which is untyped!)

Hopefully in the next rev of EJB, we can fix this.
Actions

Go to original post