Stateless bean transaction rollback

Question

HI Friends
          Iam using a stateless bean.In which some of the methods are in
          transaction having transaction attribute is "supports". Now i have a method
          A which is updating some table and iam calling another method "B" which is
          updating another table.but B method is using another connection. Iam using a
          txdatasource. If methods are in transaction if any exception occurs it
          should rollback.But is was not happening.
          A() {
          new connection();
          con.close()
          B()
          new Connection()
          con.close();
          can u help me
          

Answer 1

Thank you Salvo.I think the only way is to pass the same connection to the
          private method.
          "Jesus M. Salvo Jr." <[email protected]> wrote in message
          news:[email protected]...
          > AFAIK, no, because the container does not know about those methods. The
          > public methods in the remote interface are the only methods that the
          > container manages transaction for. Besides, why would the container handle
          > transcation for private methods when private methods cannot be called
          > remotely?
          >
          > However, calling a private method internally within method that was called
          > remotely will make the container treat them as one transaction. Your
          > private method should probably throw a SQLException, which your public
          > method catch and rethrow as an EJBException.
          >
          > Jetty wrote:
          >
          > > Other method is private method.
          > > It is possible to set transaction attribute for private methods.?
          > >
          > >
          > > "Jesus M. Salvo Jr." <[email protected]> wrote in message
          > > news:[email protected]...
          > >> In SLSB, one method is one transaction .... unless of course that
          method
          > >> was called by another EJB that started the transaction. It then depends
          > >> on how you haved setup your TX attributes.
          > >>
          > >> If the method in the SLSB was called from say a servlet, and the bean
          is
          > >> a container-managed transaction, then that method call is one
          > >> transaction.
          > >>
          > >>
          > >> Jetty wrote:
          > >>
          > >> > Update statements in each method will it come under one transaction.?
          > >> >
          > >> > "Jesus M. Salvo Jr." <[email protected]> wrote in message
          > >> > news:[email protected]...
          > >> >> How did you A call B?
          > >> >>
          > >> >> 1) Did you do create another instance of the SLSB and call B?
          > >> >>
          > >> >> 2) Or did you simply call B from A via this.B() ?
          > >> >>
          > >> >> If its 1), then each method will be handled separetely by the
          > > container.
          > >> > If
          > >> >> its 2), the container will only see your call to A, therefore just a
          > >> > single
          > >> >> transaction.
          > >> >>
          > >> >> Weblogic news server wrote:
          > >> >>
          > >> >> > HI Friends
          > >> >> > Iam using a stateless bean.In which some of the methods are
          > >> >> > in
          > >> >> > transaction having transaction attribute is "supports". Now i have
          a
          > >> >> > method A which is updating some table and iam calling another
          method
          > >> >> > "B" which is updating another table.but B method is using another
          > >> > connection.
          > >> >> > Iam using a txdatasource. If methods are in transaction if any
          > >> >> > exception occurs it should rollback.But is was not happening.
          > >> >> > A() {
          > >> >> > new connection();
          > >> >> > con.close()
          > >> >> > }
          > >> >> > B()
          > >> >> > ()
          > >> >> > {
          > >> >> > new Connection()
          > >> >> > con.close();
          > >> >> > }
          > >> >> >
          > >> >> > can u help me
          > >> >> >
          > >> >> >
          > >> >> >
          > >> >>
          > >> >
          > >> >
          > >> >
          > >>
          > >
          > >
          > >
          >