Hi Jordan, What if you create a sample with a readonly transaction by modifying the transactions-source code to incorporate that feature in any way that you feel like; then I can merge and refactor it towards something better?
Cheers, Henrik -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jordan Sent: den 12 augusti 2011 16:56 To: Castle Project Development List Subject: Re: TransactionAttribute.CustomContext Sorry, I made a typo: [Transaction(CustomContext = "SomeClass.ReadOnly ")] Should have been [Transaction(CustomContext = SomeClass.ReadOnly)] > I would try a more segregated approach. Maybe a method to return some > config model, or a separated class. My concern is that the key pair > string can easily clog the marked method readability. Hi Henry, Yes - passing strings around that like probably isn't ideal, I agree. Hence my suggestion for a constant. Another approach could be an old school style C bit flag.... *ducks* :) Jordan. -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
