Some quick comments: * There have been lots of changes in EJB3, but AFAIK the only ones relevant for Axis2 are those regarding the client view of a stateless session bean. The only major change in that area is the removal of the home interface. To cope with that you probably don't need to drop the support for EJB2. * People who use EJB3 embrace the J2EE specs and are likely to use the Web service client view (i.e. the JAX-WS support provided by the container) to expose their beans as Web Services. That is also much more powerful than the RPC stuff in Axis2. Therefore it is actually not unlikely that there are more people interested in EJB2 support (to expose their legacy beans as Web services) than in EJB3 support.
Andreas On Wed, Oct 12, 2011 at 03:03, Supun Malinga <[email protected]> wrote: > Hi folks, > axis2 supports exposing ejb2 components as web-services. Refer [1]. This is > handles via extending Message receiver to look-up jndi contexts and handle > invocations. > For eg: org.apache.axis2.rpc.receivers.ejb.EJBInOnlyMessageReceiver > org.apache.axis2.rpc.receivers.ejb.EJBMessageReceiver > Currently this implementation works with ejb 2.0. > Since ejb 3.x has changed lot(from architectural level) since ejb2 this > implementation is not usable with ejb 3. I'm working on improving it to > support ejb 3.0. > But we may have to move away from support for ejb2 while doing this. As ejb > 2 is a pretty old standard [2] and ejb 3 is widely used. > I'am still working to come up with a implementation for this. > Ideas, comments are much appreciated. > [1] http://axis.apache.org/axis2/java/core/docs/ejb-provider.html > [2] http://en.wikipedia.org/wiki/Enterprise_JavaBean#Version_history > > thanks, > -- > Supun Malinga, > > Software Engineer, > WSO2 Inc. > http://wso2.com > http://wso2.org > email - [email protected] > mobile - 071 56 91 321 > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
