To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=80100
------- Additional comments from [EMAIL PROTECTED] Mon Aug 13 13:04:36 +0000 2007 ------- @sb: 1. A lot of things that you need to rely on when doing extensive UNO programming are unspecified. This is never a justification to break backwards compatibility without need. 2. Because I need a classloader than can load classes from my extension's JAR file as well as user-configurable locations. 3. The location of the extension's jar-file is an implementation detail that depends on the organization of OOo's cache directory. So because I can't know that location in order to put it on the classpath, I think it should be there already. Furthermore, I think it's only natural if any classloader created from my component's code has access to all of the classes from my component. 4. This talks about <b>potential</b> performance and name-clash problems and is mostly about having all of OOo's JARs on the classpath. a) I don't think "potential" problems are a justification for breaking backwards compatibility b) I'm NOT arguing that all of the JARs from program/classes should be on the global classpath. I'm just talking about the extension's jar. Although if OOo were my product I'd be very careful about removing the program/classes JARs, too. You never know whose code has relied on this. I believe that it's prudent to at least do some information gathering first on how many extensions will be affected by this change. I don't know the market. Maybe there are no commercial Java extensions at all. In that case the change won't matter. But if some commercial extensions are affected, forcing customers to do a paid upgrade, then this change should be reconsidered. --------------------------------------------------------------------- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
