Issue 11688 - Direct use of Core Services framework cause JavaVM service problems
Summary: Direct use of Core Services framework cause JavaVM service problems
Status: CLOSED DUPLICATE of issue 10385
Alias: None
Product: porting
Classification: Code
Component: code (show other issues)
Version: OOo 1.0.1
Hardware: Mac Mac OS X, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: ed
QA Contact: issues@porting
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-20 16:19 UTC by pluby
Modified: 2003-03-11 17:56 UTC (History)
2 users (show)

See Also:
Issue Type: PATCH
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description pluby 2003-02-20 16:19:46 UTC 
In the OOO_STABLE_1_PORTS branch, we use 2 CoreServices functions to determine
the locale. Unfortunately, directly accessing these functions causes any AWT
code loaded by the JavaVM service in stoc/source/javavm to not detect certain
window and mouse events.

The solution is to load the CoreServices framework via osl_loadModule and invoke
the 2 functions via osl_getSymbol.

The required patchs to the sal and tools cvs modules are attached.
Comment 1 ed 2003-02-21 06:20:34 UTC 
I'm not quite sure how the CF calls themselves are causing the AWT issues.  I'm pretty sure that Java requires applications using the AWT to have their own NSApplication instance, and the OS automatically fires one up for each of my java apps coming off of the command line that use the AWT.  OOo never gets its own NSApp instance in the X11 version (nor in the current Quartz version since there's no bundle...) so all bets are off with regards to window, mouse, and keyboard events from Java, ObjC, and Carbon calls from my experience in command-line Cocoa and Carbon hacking.

Dan...any thoughts?
Comment 2 pluby 2003-02-21 07:33:18 UTC 
I have very simple patches that solve the problem. Unfortunately,
there seems to be a problem posting attachments to IssueZilla right
now. Once I can post attachments to this issue, I will do so. In the
meantime, if anyone wants to see the patches, e-mail me and I will
send them to you.
Comment 3 fa 2003-02-21 07:44:28 UTC 
Patrick,

Can you take a look at the patches in Issue 10385?
http://www.openoffice.org/issues/show_bug.cgi?id=10385

Apply the last two to sal, remove CoreServices/Java framework from tools link, then test it out and see if the problem goes away.  I've split the OS X specific code out into a separate dylib that then gets osl_LoadModule()'d when needed.

dan
Comment 4 pluby 2003-02-21 15:34:35 UTC 
Dan,

The patches in issue 10385 implement the required fix for this bug so
I am closing this issue as a duplicate of issue 10385.

BTW, the problem appears to happen whenever we directly link a
framework that is linked with the Carbon framework (like
CoreServices). Since the JavaVM framework is loaded via
osl_loadModule, the Carbon framework gets loaded first if we don't use
osl_loadModule CoreServices or other Carbon  linked frameworks.

Lastly, don't forget to add a patch for tools/bootstrp/static.mk in
issue 10385 that removes the "-framework CoreServices".


*** This issue has been marked as a duplicate of 10385 ***
Comment 5 michael.bemmer 2003-03-11 17:18:27 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details. First step in IssueZilla is
unfortunately to set them to verified.
Comment 6 michael.bemmer 2003-03-11 17:56:30 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details.