You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Supun Malinga <su...@wso2.com> on 2011/10/12 03:03:23 UTC
Support for exposing ejb 3.x as web-services
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 - supunm@wso2.com <su...@wso2.com>
mobile - 071 56 91 321
Re: Support for exposing ejb 3.x as web-services
Posted by Supun Malinga <su...@wso2.com>.
Hi,
On Wed, Nov 30, 2011 at 6:59 PM, Isuru Suriarachchi <is...@gmail.com>wrote:
> Hi Supun,
>
> Please try to create some samples as well for EJB 3.0 support.
>
sure will do.
thanks,
>
> Thanks,
> ~Isuru
>
>
> On Wed, Nov 30, 2011 at 5:11 PM, Supun Malinga <su...@wso2.com> wrote:
>
>> Hi All,
>>
>> After some work I could modify the ejb Message receivers to support
>> ejb3.0. I made this as a separate message receiver. Three new classes
>> introduced.
>> org/apache/axis2/rpc/receivers/ejb/EJB3Util.java
>> org/apache/axis2/rpc/receivers/ejb/EJB3InOnlyMessageReceiver.jav
>> org/apache/axis2/rpc/receivers/ejb/EJB3MessageReceiver.java
>>
>> Created a jira @ [1].
>> Attached a draft patch to the jira. I'll further look into do more fine
>> tuning and testing with different appservers.
>>
>> [1] https://issues.apache.org/jira/browse/AXIS2-5204
>>
>> thanks,
>>
>> On Thu, Oct 13, 2011 at 12:05 PM, Supun Malinga <su...@wso2.com> wrote:
>>
>>> Hi andreas,
>>> On Thu, Oct 13, 2011 at 12:26 AM, Andreas Veithen <
>>> andreas.veithen@gmail.com> wrote:
>>>
>>>> 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.
>>>>
>>>
>>> Agreed. will focus on sumedha's idea as well.
>>>
>>>
>>>> * 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.
>>>>
>>>
>>> AFAIU jax-ws support is only provided for stateless session beans. Also
>>> there are lots of ejb2 to ejb3 conversion tools available.
>>>
>>> thanks and regards,
>>>
>>>>
>>>> Andreas
>>>>
>>>> On Wed, Oct 12, 2011 at 03:03, Supun Malinga <su...@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 - supunm@wso2.com
>>>> > mobile - 071 56 91 321
>>>> >
>>>> >
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Supun Malinga,
>>>
>>> Software Engineer,
>>> WSO2 Inc.
>>> http://wso2.com
>>> http://wso2.org
>>> email - supunm@wso2.com <su...@wso2.com>
>>> mobile - 071 56 91 321
>>>
>>>
>>
>>
>> --
>> Supun Malinga,
>>
>> Software Engineer,
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>> email - supunm@wso2.com <su...@wso2.com>
>> mobile - 071 56 91 321
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>
>
>
> --
> Technical Lead,
> WSO2 Inc. http://wso2.org/
> Blog : http://isurues.wordpress.com/
>
--
Supun Malinga,
Software Engineer,
WSO2 Inc.
http://wso2.com
http://wso2.org
email - supunm@wso2.com <su...@wso2.com>
mobile - 071 56 91 321
Re: Support for exposing ejb 3.x as web-services
Posted by Isuru Suriarachchi <is...@gmail.com>.
Hi Supun,
Please try to create some samples as well for EJB 3.0 support.
Thanks,
~Isuru
On Wed, Nov 30, 2011 at 5:11 PM, Supun Malinga <su...@wso2.com> wrote:
> Hi All,
>
> After some work I could modify the ejb Message receivers to support
> ejb3.0. I made this as a separate message receiver. Three new classes
> introduced.
> org/apache/axis2/rpc/receivers/ejb/EJB3Util.java
> org/apache/axis2/rpc/receivers/ejb/EJB3InOnlyMessageReceiver.jav
> org/apache/axis2/rpc/receivers/ejb/EJB3MessageReceiver.java
>
> Created a jira @ [1].
> Attached a draft patch to the jira. I'll further look into do more fine
> tuning and testing with different appservers.
>
> [1] https://issues.apache.org/jira/browse/AXIS2-5204
>
> thanks,
>
> On Thu, Oct 13, 2011 at 12:05 PM, Supun Malinga <su...@wso2.com> wrote:
>
>> Hi andreas,
>> On Thu, Oct 13, 2011 at 12:26 AM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> 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.
>>>
>>
>> Agreed. will focus on sumedha's idea as well.
>>
>>
>>> * 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.
>>>
>>
>> AFAIU jax-ws support is only provided for stateless session beans. Also
>> there are lots of ejb2 to ejb3 conversion tools available.
>>
>> thanks and regards,
>>
>>>
>>> Andreas
>>>
>>> On Wed, Oct 12, 2011 at 03:03, Supun Malinga <su...@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 - supunm@wso2.com
>>> > mobile - 071 56 91 321
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>>
>>
>> --
>> Supun Malinga,
>>
>> Software Engineer,
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>> email - supunm@wso2.com <su...@wso2.com>
>> mobile - 071 56 91 321
>>
>>
>
>
> --
> Supun Malinga,
>
> Software Engineer,
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
> email - supunm@wso2.com <su...@wso2.com>
> mobile - 071 56 91 321
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
--
Technical Lead,
WSO2 Inc. http://wso2.org/
Blog : http://isurues.wordpress.com/
Re: Support for exposing ejb 3.x as web-services
Posted by Supun Malinga <su...@wso2.com>.
Hi All,
After some work I could modify the ejb Message receivers to support ejb3.0.
I made this as a separate message receiver. Three new classes introduced.
org/apache/axis2/rpc/receivers/ejb/EJB3Util.java
org/apache/axis2/rpc/receivers/ejb/EJB3InOnlyMessageReceiver.jav
org/apache/axis2/rpc/receivers/ejb/EJB3MessageReceiver.java
Created a jira @ [1].
Attached a draft patch to the jira. I'll further look into do more fine
tuning and testing with different appservers.
[1] https://issues.apache.org/jira/browse/AXIS2-5204
thanks,
On Thu, Oct 13, 2011 at 12:05 PM, Supun Malinga <su...@wso2.com> wrote:
> Hi andreas,
> On Thu, Oct 13, 2011 at 12:26 AM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> 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.
>>
>
> Agreed. will focus on sumedha's idea as well.
>
>
>> * 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.
>>
>
> AFAIU jax-ws support is only provided for stateless session beans. Also
> there are lots of ejb2 to ejb3 conversion tools available.
>
> thanks and regards,
>
>>
>> Andreas
>>
>> On Wed, Oct 12, 2011 at 03:03, Supun Malinga <su...@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 - supunm@wso2.com
>> > mobile - 071 56 91 321
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>
>
> --
> Supun Malinga,
>
> Software Engineer,
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
> email - supunm@wso2.com <su...@wso2.com>
> mobile - 071 56 91 321
>
>
--
Supun Malinga,
Software Engineer,
WSO2 Inc.
http://wso2.com
http://wso2.org
email - supunm@wso2.com <su...@wso2.com>
mobile - 071 56 91 321
Re: Support for exposing ejb 3.x as web-services
Posted by Supun Malinga <su...@wso2.com>.
Hi andreas,
On Thu, Oct 13, 2011 at 12:26 AM, Andreas Veithen <andreas.veithen@gmail.com
> wrote:
> 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.
>
Agreed. will focus on sumedha's idea as well.
> * 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.
>
AFAIU jax-ws support is only provided for stateless session beans. Also
there are lots of ejb2 to ejb3 conversion tools available.
thanks and regards,
>
> Andreas
>
> On Wed, Oct 12, 2011 at 03:03, Supun Malinga <su...@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 - supunm@wso2.com
> > mobile - 071 56 91 321
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
--
Supun Malinga,
Software Engineer,
WSO2 Inc.
http://wso2.com
http://wso2.org
email - supunm@wso2.com <su...@wso2.com>
mobile - 071 56 91 321
Re: Support for exposing ejb 3.x as web-services
Posted by Andreas Veithen <an...@gmail.com>.
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 <su...@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 - supunm@wso2.com
> mobile - 071 56 91 321
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Support for exposing ejb 3.x as web-services
Posted by Supun Malinga <su...@wso2.com>.
Hi sumedha,
On Wed, Oct 12, 2011 at 11:22 AM, Sumedha Rubasinghe <su...@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 <su...@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 - supunm@wso2.com
> > mobile - 071 56 91 321
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
--
Supun Malinga,
Software Engineer,
WSO2 Inc.
http://wso2.com
http://wso2.org
email - supunm@wso2.com <su...@wso2.com>
mobile - 071 56 91 321
Re: Support for exposing ejb 3.x as web-services
Posted by Sumedha Rubasinghe <su...@gmail.com>.
Hi Supun,
Why don't you write a separate message receiver to deal with EJB3?
/sumedha
On Wed, Oct 12, 2011 at 6:33 AM, Supun Malinga <su...@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 - supunm@wso2.com
> mobile - 071 56 91 321
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org