Closed Bug 4493 Opened 26 years ago Closed 15 years ago

LiveConnect broken due to missing libmocha functionality

Categories

(Core Graveyard :: Java: Live Connect, defect, P3)

x86
Windows NT

Tracking

(Not tracked)

RESOLVED INCOMPLETE
Future

People

(Reporter: amusil, Unassigned)

Details

With the latest OJI plugin on windows, we crash in enter_js_from_java_impl() (in mozilla/modules/oji/src/lcglue) because we cannot get a valid js context. We need a gecko equivalent to LM_GetCrippledContext(). We also need equivalents to: LM_LockJS(), LM_UnlockJS(), LM_GetMochaEnabled(), ET_InitMocha(), LM_GetJSPrinciplesFromJavaCaller(), and LM_CanAccessTargetStr(). I'm not sure how Patrick is getting around this on the Mac. I will post a link to the OJI installer here soon.
Status: NEW → ASSIGNED
Target Milestone: M6
This is tied to the security wackage I have slated for M6
Target Milestone: M6 → M7
Won't have for M6.
Target Milestone: M7 → M8
These should largely exist after the security code goes in but more work will be needed to join up the two. Pushing to M8 rather than rushing the fix.
QA Contact: cbegle → gerardok
QA Contact: gerardok → cbegle
Target Milestone: M8 → M9
A lot of this stuff in in flux. We need to discuss the correct way to do this stuff now. Adding norris to CC list and moving to M9.
Not clear how this works now. Moving down.
Target Milestone: M9 → M12
Target Milestone: M12 → M14
I honestly don't know where we stand on this right now. I'm going to push it out a bit for lack of a better plan.
What's the deal on shipping liveconnect java classes? Is this something Sun's going to do now, or will we include the jar file with our release? (Note that we're not building the liveconnect classes during our build anymore.)
Changing milestone
Target Milestone: M14 → M16
Updating QA Contact
QA Contact: cbegle → rginda
Bulk prioritizing bugs for correct milestones.
Target Milestone: M16 → M18
Still don't know where this stands. For lack of a better plan pushing to future milestone.
Target Milestone: M18 → Future
joki: What's the score with this (LiveConnect)? Is it going to be pushed out indefinitely for lack of a better plan, or is it going to come on the radar at some point? Gerv
Keywords: 4xp, mozilla1.0
This bug is meaningless at this point. I'd say we close it and mark it invalid. If there are continuing issues, let's file a more specific bug that is relevant to the current OJI implementation. Most of these issues have been addressed by the new security architecture.
I think this should be renamed simply to "LiveConnect Broken". Else the Live Connect category should be removed from Bugzilla altogether, being that all other relevant bugs for it live under OJI. All I know is, I want the Java/Javascript calling capability which Nav4 called "Live Connect", and this is the closest thing I can find to a bug expressing the fact that none of that functionality works any more (but does exist).
Much of LiveConnect does work. I am working on bug #60018 which will improve LiveConnect immeasurably. If you have specific problems to report with LiveConnect, feel free to file new bugs. The more bug reports we see, the more likely they are to get fixed. Blanket reports such as "LiveConnect Broken" aren't going to get much attention.
I look forward to seeing the fix for Bug #60018 and others. And I have filed very specific bugs and test cases, againsed very simple functionality, which is still broken: http://bugzilla.mozilla.org/show_bug.cgi?id=61488
Keywords: nsenterprise
Removing nsenterprise nomination.
Keywords: nsenterprise
Blocks: 187812
is this bug still valid ? Bugs 60018 and bug 80802 which were mentionned as related are now fixed
Assignee: joki → live-connect
No longer blocks: 187812
Status: ASSIGNED → NEW
Keywords: 4xp
QA Contact: rginda → pschwartau
This bug hasn't had any activity in the last 9 years, probably safe to mark it as incomplete...
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.