Alfia Shai 19.Apr.07 01:42 PM a Web browser Developer Toolkits7.5Windows NT/2000
I am writing a server application using IBM Sametime Community server toolkit.
The application is already monitoring chats and will monitor file transfer actions.
It will work with different clients, one of them - Sametime Connect 7.5 desktop client,
Another one - – customized client built using Java Toolkit.
The application receives all the events from clients.
This is the flow I have to get working:
-Connect from the custom client as “user1”
-Connect to the ST Connect 7.5 desktop client as “user2”
-“user1” starts a chat.
-“user2” sends a file to “user1”
Well, here the problems start!
In order to load ST service components I am using the code snippet below:
try
{
session = new STSession(userId, SametimeService.getInstance().getDispatchingThreadPool());
session.loadSemanticComponents();
new CommUIComp(session);
new ResourceLoaderComp(session);
new ChatUIComp(session);
new AnnouncementUIComp(session);
new FileTransferUIComp(session);
session.start();
}
catch (DuplicateObjectException e)
{
e.printStackTrace();
exit();
}
“user2” from ST desktop selects Tools -> Send -> File, chooses a file and presses “Send” on the clients section. Immediately Java Toolkit’s “Send File” dialog with the buttons “Accept”, “Decline”, “Browse” pops up.
But my application handles events without that dialog, moreover, it’s running on the server side and doesn’t need the GUI elements at all.
I tried to run the application without loading FileTransferUI service, i.e. commenting out
The line “new FileTransferUIComp(session);”. In this case Tools -> Send -> File didn’t work at all, “File” was inactive !
-Does it mean, that if we don’t load the UI component of File Transfer on the server side, we cannot use Send File option on the ST Connect 7.5 desktop client ?
-The second question: How can I block the Java Toolkit “Send File” dialog while processing File transfer from the ST 7.5. client?
Return to top
File Transfer and ST Connect 7.5. c... (Alfia Shai 19.Apr.07)
. . 
Print this page
