Sorry, I forget to CC the mailing list.
Yes I know, this is the page number ;-) must read: see http://www.omg.org/cgi-bin/apps/doc?formal/03-09-02.pdf chapter 2.12.1 -- Creating Transactional Object References (page 2.23) and read on page 2.24: ยท An attempt to create a transaction-aware POA with conflicting OTSPolicy and InvocationPolicy values (as defined in Table 2-4 on page 2-21) will raise the InvalidPolicy exception. regards Selon Karel Gardas <[EMAIL PROTECTED]>: > On Wed, 26 Jul 2006, Laurent Marzullo wrote: > > > Hello all, > > > > I've write a TransactionCurrent implementation. I'm now trying to propagate > > this current context to server according to policy set in the IOR of the > > target object. > > > > I've read in the spec that, if, in a server, we try to create an object > > reference > > with both: > > OTSPolicy = FORBIDS or ADAPTS > > and InvocationPolicy = EITHER or UNSHARED > > > > an exception should be raised (exception = InvalidPolicy) > > (see TransactionService 1.4 -- 2.24) > > There is no such chapter in this spec. > > Cheers, > Karel > -- > Karel Gardas [EMAIL PROTECTED] > ObjectSecurity Ltd. http://www.objectsecurity.com > --- > Need experienced, fast, reliable technical MICO support? > ---> http://www.objectsecurity.com/mico_commsup_referral.html <--- > --- > +--------------------+ + Laurent Marzullo + _______________________________________________ Mico-devel mailing list [email protected] http://www.mico.org/mailman/listinfo/mico-devel
