Hi Zev, I think your original post to the developer list may not have come through so I'm cc'ing the dev list. The correct user list email address is listed here: http://jabsorb.org/MailingLists
The callable reference tests can fail under certain circumstances if you have restarted your servlet container but still have a live browser session, depending on whether you have configured the container to persist the sessions across redeploy/restart. You are using tomcat which has session saving (on redeploy) enabled by default I believe. If it is the problem I am think about, then it is due to the way be associate the JS side references with the server side objects (using the java internal hashcode). We discussed this issue some time ago with Will and Arthur IIRC. It would require changing our method of object identity re-association in the reference code (perhaps by allocating our own id's instead of using the internal hashcode which will be changed after restarting tomcat). If you can find more information about this issue, don't hesitate to post a bug in the jabsorb issue tracker. Michael. Zev Hochberg wrote: > I've installed Tomcat 6.0.18 and jabsorb 1.3.1. > > When I first ran tests (at > http://localhost:8080/jabsorb-1.3.1/test.jsp), all ran OK under > Firefox 3.0.10 and IE 7.0. > When I first ran the unit tests (at > http://localhost:8080/jabsorb-1.3.1/unit.jsp), they all succeeded > under Firefox 3.0.10, but the Callable References and Constructors > tests failed under IE 7.0. > > Today, the Reference Test is failing under Firefox (but still runs > under IE). > Under Firefox, I get: > Running Reference Tests > > var callableRef = test.getCallableRef() > returns a CallableReference objectID=undefined > > callableRef.ping() > Exception: > > TypeError: callableRef.ping is not a function > > > Now, I'm getting non-repeatable results for unit tests. Under IE, all > fail except Client Side JSON string encoding; under Firefox, I'm now > getting results like yesterday's IE results (Callable References and > Constructors tests fail). If I restart the Tomcat service, Firefox > seems to behave differently, until next Tomcat restart. > > Any idea what's happening? > > Thanks, > ------------------------------------------------------------------------ > > _______________________________________________ > Jabsorb-user mailing list > [email protected] > http://lists.jabsorb.org/mailman/listinfo/jabsorb-user > _______________________________________________ Jabsorb-dev mailing list [email protected] http://lists.jabsorb.org/mailman/listinfo/jabsorb-dev
