I was helping someone with an application that has a stateful session bean with a remove() method with the following signature:
String remove();
(this is an action method on backing bean in a seam application)
This failed because JBoss tries to create a proxy for the object using the EJBLocalObject interface, which declares void remove().
My question is this: is JBoss doing the right thing here? Are EJB3 session beans supposed to be limited by the EJBLocalObject interface? To me this seems like a bug in our implementation, but perhaps it is the intention of the EJB3 spec?
