Using trans-attribute of Required with public vs. private bean methods

Question

          I'm having problems attempting to begin my transaction (using the Required transaction attribute
          setting in the desployment descriptor) in a private stateless session bean method. The scenario is as follows:
          public void methodA() <-- want NO transactional setting
          doSomething();
          private void doSomething() <-- want trans-attribute of Required
          doFirstPart(); <-- trans-attribute of Supports
          doSecondPart(); <-- trans-attribute of Supports
          When I do this, if I force a failure in the doSecondPart() method, the doFirstPart() database activity is NOT
          rolled back properly. If I go ahead and set the trans-attribute of methodA() to Required and change
          doSomething() to Supports, then any database activity in doFirstPart() appropriately gets rolled back
          upon a failure in doSecondPart(). Can I not initiate a transaction in a private method? Can anyone point
          me in the right direction?
          Thanks!!
          - Jim
          

Answer 1

          Here is the deal. What I was missing was this...to take advantage of the transaction attribute settings that are set in the deployment descriptor, you must call a method that is present in the remote interface. AND you must call that method through its remote interface instead of calling it locally.
          For example, I originally had the scenario below:
          public void methodA()
          doSomething();
          private void doSomething()
          Well, in the code above, there are two problems.
          1) doSomething() needs to be public and part of the remote interface;
          2) methodA() needs to call the method using the remote interface instead of calling the method locally.
          Like this:
          public void methodA()
          Object ref = jndiContext.lookup("ejb-name");
          EJBObjectType obj = (EJBObjectType) PortableRemoteObject.narrow(ref, EJBObjectType.narrow);
          obj.doSomething();
          public void doSomething()
          Or something pretty close to that. Make sense? This means that there is NO effect of putting private methods with transaction attribute values in the deployment descriptor.
          "Jim Clingenpeel" <[email protected]> wrote:
          >
          >Yes, I am using a JTS connection.
          >
          >Another interesting point. I even attempted to make the doSomething() method public and part of
          >the remote interface but the transaction still did not work properly (i.e., database activity from the
          >doFirstPart() method was not rolled back upon failure of doSecondPart()) unless my client application
          >called the doSomething() method directly. If the client called methodA() which, in turn, calls
          >doSomething(), then the transaction did not behave properly.
          >
          >Any further thoughts?
          >
          >- Jim
          >
          >"Cameron Purdy" <[email protected]> wrote:
          >>Make sure that you are using the Tx driver, not just a pool.
          >>
          >>--
          >>
          >>Cameron Purdy
          >>[email protected]
          >>http://www.tangosol.com
          >>WebLogic Consulting Available
          >>
          >>
          >>"Jim Clingenpeel" <[email protected]> wrote in message
          >>news:[email protected]...
          >>>
          >>> I'm having problems attempting to begin my transaction (using the Required
          >>transaction attribute
          >>> setting in the desployment descriptor) in a private stateless session bean
          >>method. The scenario is as follows:
          >>>
          >>> public void methodA() <-- want NO transactional setting
          >>> {
          >>> doSomething();
          >>> }
          >>>
          >>> private void doSomething() <-- want trans-attribute of Required
          >>> {
          >>> doFirstPart(); <-- trans-attribute of Supports
          >>> doSecondPart(); <-- trans-attribute of Supports
          >>> }
          >>>
          >>> When I do this, if I force a failure in the doSecondPart() method, the
          >>doFirstPart() database activity is NOT
          >>> rolled back properly. If I go ahead and set the trans-attribute of
          >>methodA() to Required and change
          >>> doSomething() to Supports, then any database activity in doFirstPart()
          >>appropriately gets rolled back
          >>> upon a failure in doSecondPart(). Can I not initiate a transaction in a
          >>private method? Can anyone point
          >>> me in the right direction?
          >>>
          >>> Thanks!!
          >>>
          >>> - Jim
          >>
          >>
          >