"ron.sigal(a)jboss.com" wrote :
| 1. Does anyone care about having this feature?
|
| 2. This change would mean that the InvocationMarshaller would be used on the server
side when returning a response and InvocationUnMarshaller would be used on the client side
to unmarshal the response. Would adding and removing transaction context in the
server-to-client direction have any implications?
|
| 3. Since EJB3 handles transaction information in an interceptor and doesn't, by
default, configure any marshaller or unmarshaller, am I right that this issue is
irrelevant to EJB3?
|
|
From JBM POV, we only use the bisocket and http transports, so as long
as it doesn't effect those transports, we don't care
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135268#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...