[
https://issues.apache.org/jira/browse/CXF-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharath Ganesh resolved CXF-1759.
---------------------------------
Resolution: Invalid
Assignee: Bharath Ganesh
Exposing an EJB 3.0 implementation as a Web Service, would mean you would want
to leverage the EJB 3.0 container services for the exposed web service endpoint
- like Transaction support, instance pooling, Java EE DI etc. And here if you
need to use CXF as the SOAP engine, your EJB 3.0 container should integrate
CXF. CXF as such is a JAX-WS complaint SOAP stack.
It does not implement JSR-109 specification which talks about exposing EJB as a
JAX-WS web service endpoint.
There are EJB 3.0 containers which implement JSR 109 and use CXF as the Web
Service stack - like- Apache Geronimo and Pramati Server.
> CXF and EJB 3.0 integration support
> -----------------------------------
>
> Key: CXF-1759
> URL: https://issues.apache.org/jira/browse/CXF-1759
> Project: CXF
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 2.1.2
> Environment: WebLogic 10, Spring Framework 2.5
> Reporter: Sripathi Acharya
> Assignee: Bharath Ganesh
>
> Hi,
> I would like to expose an EJB 3.0 interface as a webservice using CXF 2.1.2.
> I prefer using EJB and WebService annotation for the same implementation
> class.
> I'm not able to find any documentation on how to achieve this or this
> integration is possible with CXF. WebLogic provides the means to expose EJB 3
> as webservice, but I would like to use CXF implementation to achieve this.
> Can you please provide some documentation on this.
> Sripathi.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
