Does it need anything?
Clearly states that it should throw an IllegalStateException.
It also states in the spec for the various session bean types:
"Invoking the getMessageContext method is disallowed in session bean methods that
were not invoked by the container through the session bean’s web service endpoint."
The whole dependency on the JAX-RPC API class(es) remains a bummer though.
On 04/19/2012 05:17 PM, Marina Vatkina wrote:
Yes, we hadn't addressed it yet, but we will not be removing parts of the deployment descriptor, nor parts of the javax.ejb API for the optional features. It's on my todo list to write this up, but if anybody volunteers to do so, you are welcome.
Jeremy Bauer wrote:
Apologies if this has already been discussed. I couldn't find anything in JIRA or in my mail archive.
While JAX-RPC will be made optional in 3.2, am I correct in assuming that vendors will minimally have to continue to provide the javax.xml.rpc.handler.MessageContext interface for SessionContext? In other words, even though JAX-RPC support will be optional, there'll always be a bit of JAX-RPC hanging about?
|Carlo de Wolf||04/19/2012|
[ejb-spec users] [jsr345-experts] Re: JAX-RPC MessageContext in SessionContext