To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=114604 Issue #|114604 Summary|Context classpath not established when calling UNO ext |ensions in Java Component|framework Version|OOO320m19 Platform|Macintosh URL| OS/Version|All Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|code Assigned to|tm Reported by|bimargulies
------- Additional comments from bimargul...@openoffice.org Sun Sep 19 21:16:35 +0000 2010 ------- When OO 3.2.1 calls into an UNO extension coded in Java, Thread.currentThread().getContextClassLoader() return null. This in turn causes various standard JRE facilities to exhibit some, well, surprising behavior. For example, the JAX-WS API (javax.xml.ws.Service). If you put a JAX-WS implementation into the classpath (using the OO classpath dialog), and then try to create a proxy, JAX-WS will succeed in finding the SPI file, but fail to find the corresponding class. Other malfunctions can be produced fairly easily. It would be more standard, and avoid all this confusion, if OO would call setContextClassLoader appropriately. --------------------------------------------------------------------- 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...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
