To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102313
------- Additional comments from msmit...@openoffice.org Thu May 28 15:29:13 +0000 2009 ------- Thanks for the help, it appears to have resolved the problem. The defaultBootstrap_InitialComponentContext() approach had worked with all the OO 2.x releases I have tested. On using socket connections, I have not been able to get the DocumentLoader example or our Service to work with a socket connection using OO 2.4, OO 2.4.1, 00 3.0.1 or OO 3.1. I went back once again this morning and recompiled the original 3.1 SDK DocumentLoader example and tried to run it. I got the following error message: "Connector : couldn't connect to socket (WSANOTINITIALISED, WSAStartup() has not been called)" This is the same error message I have been getting since OO 2.4 when trying to use the socket connection. It works fine with releases prior to OO 2.4. Am I doing something wrong? We are using the socket connection in production with OO 2.1. I would like to stick with the socket connection when we introduce a new version OO into the production, instead of changing to a pipe connection. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@api.openoffice.org For additional commands, e-mail: issues-h...@api.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
