Yan Zhou wrote:I thought all I need to do for EJB3.0 is to use the standard Java compiler to compile it and deploy it.
There is no change in descriptor file because it is optional to EJB3.0. I am not converting existing EJB2.0 to EJB3.0, what I hope to do is to have existing EJB2.0 continue working as it, and add EJB3.0. What would be the process for that?
Ah ! after perusing through your question I have come to realize that I misunderstood it. I am not sure about the interoperability of EJB 3 with EJB 2. I have not done it myself. Is it possible ? hmmm... I do not know that either. But why do you want to deploy different EJBs on the same app ? It is likely to cause maintenance headaches down the line.
Here is what you can do though. Try deploying the EJB 3 as a standalone and check if that deploys. This will help determine any interoperability problems. Compare with a sample EJB 3 in weblogic and check if yours is different by any means.
If you found the answer to your question let us know. I would like to know if EJB 2 and 3 can work together on the same app. In theory atleast, that might be possible
