I follow what your saying and agree with the need but I still need to drill down into the implementation at which point I might be back. Although this solution works for j2ee components that have the notion of a reference to proxy semantic through ejb-refs, we really need transparent transformation of protocol proxies for the 4.0 codebase. What thought has been given to this?
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Francisco Reverbel" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, March 05, 2003 9:28 AM Subject: Re: [JBoss-dev] jboss_3_2.dtd updated > I'll try to be more precise. In order to interact with Y, X must use a > reference to Y. This reference determines the protocol over which the > interaction will take place. > > If X calls Y for its own consumption, without obtaining from Y any > reference that may be returned to the caller of X, then X is free to > interact with Y using whatever reference (protocol) it wants. > > If X is called via IIOP and interacts with Y in order to obtain a > reference that may be returned to the caller of X, then X and Y ougth > to interact via IIOP, possibly optimized for local invocations. > > Invoker-specific (ReferenceFactory-specific, really) ejb-refs allow you > to set things up so that X uses an IOR for Y if it was called via IIOP, > and uses a Java proxy for Y otherwise. > > Cheers, > > Francisco ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
