Any thought about enabling existing EJB deployment in Spring

[shengsong]

Anybody thought about enable Spring to deploy an existing EJB-JAR? I didn't mean to access EJB component in the EJB way, it will become a common Spring component.
Let's make things simple, say we just want to cohost SLSB. Many biz logics are wrapped through SLSB these days. So the quickest way to adopt Spring is to reuse the biz logic in the EJB component, say the EJBContext impl class can be reimpled on Spring. EJBHome is trivial and not needed, if EJB is no longer access as EJB.

The main task will be to parse the EJB DD and convert to Spring DD, and generate necessary interceptors based on Aspect? And provide a EJBContext impl class....

Any other thoughts? I think this makes sense. The idea is to enable deploying EJBs purely in a Spring Container, while if some customers demand proprietary Container, it can still be reused in other AppServers.

[Costin Leau]

To do your proposed solution, Spring has to become an application server by itself. The EJB specs contain a lot of subtilities - think of all the xml files associated, the EAR structure and the restriction you have inside them.
It's a lot easier to externalize the logic from the SLSB in separate POJOs and then simply reuse these ("expert one-on-one" recommends the same thing).