Hi. I've been reading through the mailing list archives for jboss-dev and jaws and i haven't found a solution to a couple of problems i am having. Description of problem #1. I am using JBoss to deploy an ejb. This ejb is called Book. (If any of you are familier with the tutorial in the WLS this is the book from the library example) The Book has a few finder methods. FindBorrowed, FindAll, FindUnBorrowed. It also has methods to set the status of the book if someone wants to borrow it. Finally, it has a bunch of methods to get properties of the book. (Title, Status, Subject, etc...) The books' information are all kept in a cloudscape database. I was able to set up all the connectionPools and all the other stuff, everything seems to work fine. When i call FindAll, or FindBorrowed, or FindUnborrowed, it works great. Here is my problem. if i actually borrow a book, and change it's status from UnBorrowed to borrowed(all through calling methods of the Book bean) , when i call FindBorrowed, the Enumeration of books returned does contain the newly borrowed book, but when i call getStatus on the newly borrowed book, the status returned is 'Unborrowed'. As well, if a borrowed book is returned, it shows up in the unborrowed list of books, but it's status is still 'borrowed'. the behaviour seems to suggest that the query from the database returns the list of books, and when JBoss is creating the Enumeration, it somehow uses cached books to construct it, and doesn't update all the information in those cached books. ??? Description of Problem #2. That's not all, i also have a strange problem with the jaws stuff. i understand that tuned-update is supposed to be an optimization so that if it is set to true, only the changed data is written out. My understanding is that if you set tuned-update to false, everything should be written all the time. however, in my experience, when i set tuned-update to false, nothing gets writted to the database at all. this is very puzzling. i am currently running jboss beta2 (downloaded the binaries off the jboss site). One last thing i would like to point out, i realize that one could claim that the caching problem could be in other areas of this application i am writing, but in our experience, the other components do work correctly when we used wls to deploy the ejb. the only part we have changed is that we now use JBoss to deploy the ejb and make the connection to the database. I hope this post of mine makes sense. i'd appreciate any help i can get. has anyone else ever experienced strange problems like this? Kevin Lo.
