Hi sumedha, On Wed, Oct 12, 2011 at 11:22 AM, Sumedha Rubasinghe <sumedh...@gmail.com>wrote:
> Hi Supun, > Why don't you write a separate message receiver to deal with EJB3? > yes, this is possible. But then we need to do a refactor and get common stuff out from the ejb2 and ejb3 message receivers. I believe most of the fundamental things won't change here. thanks, > /sumedha > > On Wed, Oct 12, 2011 at 6:33 AM, Supun Malinga <sup...@wso2.com> 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 - sup...@wso2.com > > mobile - 071 56 91 321 > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org > For additional commands, e-mail: java-dev-h...@axis.apache.org > > -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com <sup...@wso2.com> mobile - 071 56 91 321
