----- Original Message ----- From: "David Jencks" <[EMAIL PROTECTED]> To: "jboss-dev" <[EMAIL PROTECTED]> Sent: Sunday, December 08, 2002 6:16 PM Subject: [JBoss-dev] Invokers (jboss 4)
> I've been studying the invokers while working on the xid-based transaction > propagation and plan to do some refactoring if there are no strong > objections. > > 1. I plan to make both the client (sending) and server (receiving) halves > of the invokers layered with aspects or interceptors. This will enable > reuse of everything except the transport layer across most invokers. > So do you have a prototype configuration for a stateless session bean using RMI as the transport here to demonstrate what this is going to entail? > 3. In order to use the work import contracts, I plan to make all the > invokers asynchronous, as the trunk invoker is today. The Work object will > include both the code to call the mbean target (i.e. ejb) and the > information necessary to return the result back through the transport > mechanism. It's possible that separate inbound and outbound > interceptor/aspect stacks may be desirable. > This would seemingly add a lot of complexity to synchronous configuration. Can't both synchronous and asynchronous be used? How is this going to mesh with inherently syncrhonous protocols like http and jrmp? > 4. There has been some discussion about two way transport, as implemented > in the trunk invoker. It seems to me that any way of calling an ejb has in > it 2 communication channels, one in each direction. If these are based on > accessible sockets, the channels can be used in the opposite direction and > order, thus providing two way transport. I propose to provide this two way > transport when the underlying transport supports these separable transport > directions (for instance, my impression is that rmi does not). If there > are problems with this approach I'd like to know about them. If you > disagree with this approach please explain why the in and out streams from > a socket should not be used in both directions for this purpose and explain > in at least a little detail an alternative approach. One thing that you need to be careful of in splitting the return channel from the request channel is maintaining the thread context class loader for the marshalling of return values and exceptions that are coming from the deployment jars. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
