> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Ole > Husgaard > Sent: Wednesday, February 19, 2003 9:11 AM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] TxInterceptor split is really really good > > > The OTS policy only supports the equivalents of never, supports and > mandatory. Since the policy is included in the address (IOR), the > client knows if it needs to send a tx id along with the call. > Unfortunately, the OTS policy can only be defined at the object level > and not at the method level, I think. >
OTS only supports the equivalents of never, supports and mandatory, but this shouldn't prevent us from having a CORBA client talking to an EJB and the EJB provides support on a per method basis for Required, RequiresNew, and NotSupported. Again, this is where I think Davids design is flawed. EJBs, MBeans and later AOP should NOT have to define separate interceptor chains for the Server for each Transport mechanism. Bill ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
