UIX/BC4J: Update/Caching problem?

Question

Dear all,
we are using UIX with BC4J to build a web application that models sort of a workflow. We factored the application into multiple application modules nested in one root module. We have two VOs (VO1 and VO2) that are both based on the same EO. Both VOs live in different application modules (AM1 and AM2). One UIX page adds rows to the EO through VO1 (using Java to handle the UIX event), another UIX page displays the new rows through VO2 (using bc4j:table).
Now during testing I encounter the following problem: After I add rows in VO1 and do AM1.getTransaction().commit(), I don't see any changes in VO2. As a workaround, I do VO2.executeQuery() immediately after the commit, but shouldn't the changes be automatically propagated if the VOs are based on the same EO?
Is there a way to notify changes across user/session borders, e.g. if user A updates VO1, user B immediately sees the changes in VO2?
Many thanks for any help!
Markus.

Answer 1

I think the behaviour you describe is normal and there are reasons for it: see a section entitled "How Does the Business Logic Tier Cache Data?" in the help. (In particular, the "Multiple view object instances and update, delete and insert behaviour" near the bottom.)
Basically, because BC4J doesn't have an arbitrary-SQL evaluator it can't generally tell whether an entity belongs in a different view or not.
I recall having read in these forums before (Sung Im, I think) that you're allowed to add a row to more than one view (and that only one entity will be created) but I think the views have to be of exactly the same format.
HTH
Mike.