Hi, Yes you're right, I used JDBC directly the second time...
It would be difficult to use the Entity Bean method to access the updated value... e.g., I am updating the score of a question in a table using the Entity Bean. Then I am updating a total score and an average score using some computation in the sql...in the select, i use sum and decode on the updated values. In another scenario, I am performing a batch update, using an sql statement, where the updated column is in the where clause. SO, I will try to explore the not caching option if it works... Thanx n Regards, Vibha ----- Original Message ----- From: "Thai Thanh Ha" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, April 04, 2002 5:00 PM Subject: Re: Problem with Entity Bean > Hi Vibha, > > I think you used JDBC to work directly with database. Is it right? you > should tell the application server that entity bean should not be catched by > the application server. The application server often cache data for > efficiency (I don't know how to do that on iPlanet server). Or you should > not use JDBC directly to work with values the entity bean managed, you > should use EJB technology to access to that data (use methods of the entity > bean to find and update data). > > Regards, > Thai > > -----Original Message----- > From: Vibha Jindal [mailto:[EMAIL PROTECTED]] > Sent: Thursday, April 04, 2002 3:56 PM > To: [EMAIL PROTECTED] > Subject: Problem with Entity Bean > > > Hi, > > I am using iPlanet Application Server for my application. > > I am encountering a problem. I have used Bean Managed Persistence for my > beans. > > Ina method of teh Session Bean, I am invoking the set method of the Entity > Bean, in which set the values to the changed ones. Then, in the Session > bean's method, I perform an operation, for which I query the table that the > Entity Bean had updated. At times, it seesms that the ejbStore() method is > called later in time, because I still get the old value. When I run it > again, I get the value that was previously updated. i.e., the next step is > being performed first befor eteh update (ejbStore). Has anyone encouneterd > such a problem? > > Regards, > Vibha > > =========================================================================== > To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff > JSP-INTEREST". > For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST > DIGEST". > Some relevant FAQs on JSP/Servlets can be found at: > > http://archives.java.sun.com/jsp-interest.html > http://java.sun.com/products/jsp/faq.html > http://www.esperanto.org.nz/jsp/jspfaq.jsp > http://www.jguru.com/faq/index.jsp > http://www.jspinsider.com > > =========================================================================== > To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". > For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". > Some relevant FAQs on JSP/Servlets can be found at: > > http://archives.java.sun.com/jsp-interest.html > http://java.sun.com/products/jsp/faq.html > http://www.esperanto.org.nz/jsp/jspfaq.jsp > http://www.jguru.com/faq/index.jsp > http://www.jspinsider.com =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com
