Closed Bug 40108 Opened 24 years ago Closed 24 years ago

xpidl should generate Java interfaces in separate files

Categories

(Core :: XPCOM, defect, P3)

Product:
Core
Component:
XPCOM
Type:
defect

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: braden, Assigned: sdv)

Details

If an IDL file includes more than one interface definition, -mode java will
output all the interfaces in the same output file. javac doesn't like this. It
wants each interface in a separate file named "InterfaceName.java".
The Sun folks have been working on the xpidl backend.

Reassiging...
Assignee: mccabe → frankm
Frank Mitchell no longer works at Sun and his email is bouncing. Reassigning
his 21 bugs to george for reassignment.
Assignee: frankm → drapeau
Will work on this after PR 2.  Working on beginnings of this now.
Target Milestone: --- → M19
Re-assigning to lead engineer of BlackConnect, Igor Kushnirskiy.  Igor's group
is working on XPIDL modifications; perhaps this can be added to the list, or at
least evaluated here to see if/when this is possible.
Assignee: drapeau → idk
Reasigning to Denis Sahrypov.
Den will you take a look at this
Assignee: idk → sdv
fixed. the sources to compile can be found 
at mozilla/java/xpcom/java/xpidl
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Ack.

This means that you've forked the xpidl sources for the Java backend.

I would recommend against this.  Changes and fixes are still going into xpidl,
and many of them are also applicable to the Java backend.  There are IDL
verification functions in xpidl_util.c that the Java backend can use.

Is there a reason that the Java backend needs to be under
mozilla/java/xpcom/java/xpidl?  Why not use the backend already working under
mozilla/xpcom/xpidl?  We'd be happy to have you hacking on it.
Component: xpidl → XPCOM
QA Contact: mike+mozilla → xpcom
You need to log in before you can comment on or make changes to this bug.