Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4210127

Customer wants java "libawt.so" linked against libXm.so.4

    Details

    • Subcomponent:
    • CPU:
      generic
    • OS:
      solaris_7

      Description

      discussed on the phone, our product (SL-GMS) is a
      "graphical modeling system" toolkit with which our customers
      build applications (on a variety of systems) which typically
      contain graphical objects which change appearance in response
      to changing data.

      there is a lot of system independent as well as system dependent
      legacy C code which implements our system. on solaris we support
      both "raw X" and "Xt-based" applications in either single-byte
      or X-Input-Method environments.

      we have written a javabean which uses the deprecated-but-as-
      far-as-we-can-tell-absolutely-necessary "getPeer()" to access
      the native windowing structures.

      on windows we get a window handle using the peer's "getHWnd"
      method which works fine.

      on solaris we get both the X window ID using "getDrawable" and
      the X Display pointer using "GetDisplay".

         * our "raw X" version opens a separate Display connection,
      and creates an X window on that Display using java's
      Drawable as the parent.

      this works fine.

         * our "Xt-based" version, however, cannot make use of a
      separate Display connection, since the widget hierarchy
      to which we need to attach our code already exists in
      the peer. for example, the tree we're seeing in our
      test program is:

      java_dpy: 0xedc58
      java_win: 0x5c00043
      java_widget: 0x13de10 => 'DrawingArea'
      Parents:
      widget=0x1173f8 window=0x5c00041 type='DrawingArea'
      widget=0x117280 window=0x5c00040 type='DrawingArea'
      widget=0xffd30 window=0x5c0003f type='Form'
      widget=0x115028 window=0x5c0003e type='WMShell'

      what we would like to do is to create a child of
      "java_widget" which we can draw into, attach event
      handlers to, attach additional widget children, etc.


      i believe that we need a multi-thread safe version of
      Motif to allow both awt's thread and our thread to make
      use of these widgets, Display pointer, and application
      context.

      (by the way, what seems to happen using libXm.so.3 is that
      the Xm/Xt querying we do works, but exercising the Display
      connection causes a hang and eventual crash..)

      so, can i get a java "libawt.so" linked against libXm.so.4?

      thanks,

        Attachments

          Activity

            People

            • Assignee:
              ksrini Kumar Srinivasan
              Reporter:
              rletteri Robert Letteri (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Imported:
                Indexed: