Blitz and RIO
RIO [en] is bundled with some few services such as the ones in the Jini [en] reference implementation. But instead of using Outrigger (the JavaSpace implementation from the RI), I wanted to use Blitz [en].
Blitz [en] is in fact distributed with a sample configuration file for RIO [en], but unfortunately this configuration was not setting up ServiceUI [en] and not giving a name to the space, so the dashboard tool was not usable. I have altered the default configuration in order to solve those issues. I have sent the new configuration file to Dan Creswell [en] (the one behind Blitz [en]) and it will be included in the next version.
Meanwhile, you can easily download Blitz configuration for RIO from my website.
November 3rd, 2004 at 4:40 am
When I click the the “Launch org.dancres.blitz.serviceui.DashboardUI$Factory”, a tiny new window is popped up that seems to be the service ui for blitz. It is so small that I can’t tell what the label says and the pane contains no content and is only about 3 pixels tall. It cannot be resized. The taskbar label reads, “Blitz dashboard: v1.2 [dancres]”, so it appears the ui is being at least partially invoked. The console for the opmon reads as follows, “Blitz Dashboard: Developed in association with Inca X (www.incax.com) “. No visible errors occured. Any suggestions why the service ui is opening up in a tiny new window with no content in it and can’t be resized? I used the new xml file you created and am using Rio 3_1RC1. Thanks for the response.
November 3rd, 2004 at 10:17 am
This is a known bug in RIO 3.0.1. The fact is that RIO do determine the size of the window by asking for the preferred size of the panel. Unfortunately Blitz do not set properly this size, hence a “0×0″ window
It should be fixed in RIO 3.1-RC1 (should call getSize() instead) and in the next version of Blitz too, although I have not checked.
November 3rd, 2004 at 8:22 pm
I fixed the problem. It appears that in rio3.1-RC1 the getSize() call was added to the launchFrameUI function to alleviate the preferredSize problem you mentioned, but the frame.pack() call was left in (which seems to be the source of the problem). I commented out the frame.pack() line and the Dashboard UI displays properly! Is the frame.pack call going to be needed by other Service UIs?