There were only StatelessSessionBeans in the CXF factory because:
===
The client of a stateless session bean may be a web service client.
Only a *stateless *session bean may provide a web service client view.
I'm not sure why this is. (in regards to the above specification detail).
JAX-WS calls for support for sessions. The web service mechanism should
easily allow for the
identification of which session, before an instantiated (Client-facing)
Business Interface implementing
EJB bean is directly engage
Hi Everyone,
I just joined this group and hoping to help out with some development.
I have setup the project with eclipse and looking at the Jira tickets.
If you think there is a specific task or jira ticket that can help me
understand the system more, please let me know.
To begin with I am lookin
Ryan - this is a CXF dev list so if you just intend to think aloud
then the dev list is not the best place to do it :-), I'm sorry if I
misunderstood your "no comment necessary" bit in the subject.
Once again, I like the fact you are trying to approach the issue
fundamentally, but IMHO you have to
Then just have a stateless session bean exposed as JAX-RS endpoint too
for a start
On Sun, Jul 17, 2011 at 5:54 PM, Ryan Zoerner wrote:
> There were only StatelessSessionBeans in the CXF factory because:
>
> ===
> The client of a stateless session b
