This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Although I never tried this but I think it should n't work if you define this method in Remote Interface. Because its a life cycle callback method which is implemented by container. but if you define it in Remote interface then you need to implement it like other Business methods.
I was just going thru a EJB book which specifies the methods that needs to be specified in each interface and the role of each interface. which means specifying ejbCreate method in Remote interface will violate these rules. Moreover, RemoteHome interface extends EJBHome interface and must specify create,remove and finder(for entity bean) methods.
You would "break the rules" doing it. The EJB container is responsible for creating EJB objects, not you. Home interface is dedicated to creation and destruction. You cannot decide to replace it by your own functions, as the container must be able to decide if it will create and object or reuse an existing one, etc..., etc.
So, this is definitively not a good idea. Even if I've never tried it, I believe exposing ejbCreate in the Remote interface would call the ejbCreate of your bean. But you would miss all the added value of the container, so I'm quite sure the EJB would not be properly created and instanciated.
/ JeanLouis<br /><i>"software development has been, is, and will remain fundamentally hard" (Grady Booch)</i><br /> <br />Take a look at <a href="http://www.epfwiki.net/wikis/openup/" target="_blank" rel="nofollow">Agile OpenUP</a> in the Eclipse community