posted 20 years ago
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