Re: How to create and use a Transaction Broker

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Thunder (mbowman_at_verticalworks.com)
Date: 06/04/04

  • Next message: Thunder: "Re: COM + and the correct App.CONFIG file???" 
    Date: Fri, 4 Jun 2004 16:56:27 -0700

    Florin,

    The NEW keyword is not having the affect I desire. Perhaps I did not state
    the problem correctly.

    "How does one go about creating serviced components in the context of
    another serviced component- all from the front end???"

    Consider this...

    I have 3 simple serviced components in COM+. One component is called the
    Transaction Broker and it "requires a new transaction". The other two
    components actually do the work. All three components are instantiated by
    the FORM(client)

    The usage scenario is simple... A form- on the client- instantiates the
    Transaction Broker. The form then instantiates the other two serviced
    components and tells them to SAVE(after doing some work). Problem is that
    the components are not "in the transaction".

    The behavior I am looking for is to have the two serviced components
    "enlist" in the transaction of the Broker object so that I can roll back.
    Currently this is not happening.

    How does one go about creating serviced components in the context of another
    serviced component- all from the front end???

    When

    "Florin Lazar [MSFT]" <florinlazar@online.microsoft.com> wrote in message
    news:un9EjmTSEHA.3988@tk2msftngp13.phx.gbl...
    > Hi Michael,
    >
    > Simply using new to create the other serviced components should be enough.
    > I'm assuming that these other components are marked Transaction "Required"
    > or "Supported".
    >
    > Regards,
    > --
    > Florin Lazar - Microsoft - [ http://blogs.msdn.com/florinlazar ]
    > Please do not send email directly to this alias. This alias is for
    newsgroup
    > purposes only.
    > This posting is provided "AS IS" with no warranties, and confers no
    rights.
    >
    > "Thunder" <mbowman@verticalworks.com> wrote in message
    > news:ex$7Bx%23REHA.1160@TK2MSFTNGP09.phx.gbl...
    > > Greetings,
    > >
    > > I am trying to create a Transaction Broker component that can be
    > > instantiated to "setup" a new transaction. Once the TransBroker
    > establishes
    > > a new transaction, I would like to call my other serviced components and
    > > have them enlist in the transaction of the TransBroker.
    > >
    > > This is proving to be difficult as I cannot find the correct way to
    > > instantiate the "other" components within the context of the
    TransBroker.
    > >
    > > In the old days, we could use ObjectContext.CreateInstance(), but I
    cannot
    > > find a similar method that will allow me to create "serviced components"
    > > within the context of the primary object- the Trans Broker.
    > >
    > > Any ideas would be appreciated.
    > >
    > > -Michael
    > >
    > >
    >
    >

  • Next message: Thunder: "Re: COM + and the correct App.CONFIG file???"

    Relevant Pages

    • Re: How to create and use a Transaction Broker
      ... Simply using new to create the other serviced components should be enough. ... I'm assuming that these other components are marked Transaction "Required" ... > have them enlist in the transaction of the TransBroker. ... > instantiate the "other" components within the context of the TransBroker. ...
      (microsoft.public.dotnet.framework.component_services)
    • Re: How to create and use a Transaction Broker
      ... If your front end instantiates the transaction broker component and the 2 ... > I have 3 simple serviced components in COM+. ...
      (microsoft.public.dotnet.framework.component_services)