On Tuesday, January 21, 2003, at 09:43 AM, Francisco Reverbel wrote:
Does this constrain non-iiop invokers in any way?On Tue, 21 Jan 2003, marc fleury wrote:And, finally, why did you tightly couple distributed tx logic with invoker's implementation? Why is not it possible to write an interceptor that does distributed tx stuff that you've described but in invoker independent way?If only ole husgaard was awake :) I have been asking the same question for about a year and a half. I forgot the reason, which probably means it wasn't real, but Ole seemed to have one...Transaction propagation over IIOP is a reason. CORBA specifies that transaction info goes in the "service context", which is a field of the IIOP request.
Do we control anything about the client side of the iiop invoker? How about if the client is java rather than c++? Are there some short yet informative docs on how iiop into jboss works?
thanks
david jencks
Francisco ------------------------------------------------------- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
------------------------------------------------------- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
