I am using MS MCV with Rhino Commons and ATM. No issues. On a
related point, in case you have not figured it out yet, when using
UnitOfWorkApplication with MVC you need to to do like this:
http://lunaverse.wordpress.com/2008/07/13/rhino-commons-with-ms-mvc/
On Oct 11, 1:10 pm, "Will Shaver" <[EMAIL PROTECTED]> wrote:
> That was sarcasm, I always use the trunk of everything. Thanks for your
> help, I'll look into ATM when I'm back at work on Monday.
>
> On Sat, Oct 11, 2008 at 6:05 AM, Craig Neuwirt <[EMAIL PROTECTED]> wrote:
> > You can use ATM TransactionFacility with ActiveRecords TransactionScope and
> > that should work fine. Just don't use it with With.Transaction of
> > RhinoTransactionFacility unless you can apply the fix.
>
> > On Fri, Oct 10, 2008 at 7:02 PM, Will Shaver <[EMAIL PROTECTED]>wrote:
>
> >> trunk... is there any other way? ;-)
>
> >> On Fri, Oct 10, 2008 at 4:42 PM, Craig Neuwirt <[EMAIL PROTECTED]>wrote:
>
> >>> I agree with Ayende. I am using it on my current problem without any
> >>> issues. I use ATM whenever possible and With.Transaction when I need fine
> >>> grained transaction control. The one important thng I observed is don't
> >>> mix standard AR TransactionScope usage with Rhino Transactions. The
> >>> handle
> >>> the concept of current transaction a little differently. I use
> >>> RhinoTransactionFacility.
>
> >>> Make sure you use rhino trunk because I fixed a few transaction issue a
> >>> few days ago that are need to ensure correct behavior if rollback occurs.
>
> >>> craig
>
> >>> On Fri, Oct 10, 2008 at 3:26 PM, Will Shaver <[EMAIL PROTECTED]>wrote:
>
> >>>> I've spent a couple of days browsing Rhino-Tools and am mad at myself
> >>>> for not doing so six months ago. :(
>
> >>>> I'm thinking of incorporating RT into my project, but haven't seen any
> >>>> posts on using it with asp.net mvc.
>
> >>>> Does anyone have experience or recommendations for using the
> >>>> [Transactional][Transaction] attributes with asp.net mvc controllers?
>
> >>>> In reviewing the code, I also noticed:
>
> >>>> #1) It looks like in some places there is something like:
>
> >>>> using (UnitOfWork.Start())
> >>>> {
> >>>> //perform actions
> >>>> UnitOfWork.Current.TransactionalFlush();
> >>>> }
>
> >>>> #2) where other places it is something like:
>
> >>>> With.Transaction(delegate
> >>>> {
>
> >>>> //perform actions
>
> >>>> });
>
> >>>> Which has two different modes -> when in a trasaction it doesn't
> >>>> commit, but when not in a transaction it does commit.
>
> >>>> with #1 you could be querying outside of a transaction. With #2 are
> >>>> you assuming that you'll always finish the transaction at some nesting
> >>>> level, so don't commit if we already have one?
>
> >>>> When using flushmode.Commit, is work done inside a disposed
> >>>> transaction lost for a later request?
>
> >>>> Hopelessly behind
> >>>> -Will
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Rhino Tools Dev" 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/rhino-tools-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
