| Summary: | [UICallback] Application crashes after activating a UICallback | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Austin Riddle <austin.riddle> |
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | P3 | ||
| Version: | 1.5 | ||
| Target Milestone: | 1.5 M1 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Austin Riddle
The controls demo will seems to come up, but other apps won't even load the first time. To reproduce: If you enable a UI Callback in preStartup() of an application workbench advisor, it will crash the app when the client tries to load. The first time, your will get a server session timed out message with a javascript error, and then if you refresh the page, the above noted exception occurs. After more testing it seems that you cannot enable a UICallback at all without crashing the app. From the controls demo you can just go to the ProgressBar tab and click "Start Background Process". Anything you do after will crash the app. The CVS was broken in between, but the issue should be fixed now. We forgot to update the UICAllBack URL in the client-side code when we moved the UICAllBack stuff to a new package. Could you check again with CVS HEAD? (In reply to comment #5) > The CVS was broken in between, but the issue should be fixed now. We forgot to > update the UICAllBack URL in the client-side code when we moved the UICAllBack > stuff to a new package. Could you check again with CVS HEAD? Hi Ralf, it does indeed work again now. :-) I had to test in debug mode because you didn't check in an updated client.js. I tried to recompress the client myself, but the compressor is complaining about corrupt files. Just FYI. (In reply to comment #6) > I had to test in debug mode because you didn't check in an updated client.js. client.js rebuilt and committed. Thanks, Ivan! |