Slashdot Mirror

← Back to Stories (view on slashdot.org)

Sun's JDIC And JDNC: A Cross-Platform ActiveX?

Posted by timothy on from the sun-is-busy dept.

Espectr0 writes "eWeek is reporting that last week, Sun Microsystems Inc. licensed a pair of the underlying technologies of the Java Desktop System under the open-source LGPL (GNU Lesser General Public License). The two projects, JDNC (JDesktop Network Components) and JDIC (JDesktop Integration Components), are essentially to Java application developers what Microsoft's ActiveX and COM were to Windows developers--an architecture for creating easily configured application components and for integrating with the functionality of the local operating system and other applications."

10 of 28 comments (clear)

  1. Not Quite by pnatural · · Score: 4, Informative

    This quote is misleading:

    The two projects, JDNC (JDesktop Network Components) and JDIC (JDesktop Integration Components), are essentially to Java application developers what Microsoft's ActiveX and COM were to Windows developers--an architecture for creating easily configured application components and for integrating with the functionality of the local operating system and other applications."

    From the JDNC project page:

    The goal of the JDesktop Network Components (JDNC) project is to significantly reduce the effort and expertise required to build rich, data-centric, Java desktop clients for J2EE-based network services. These clients are representative of what enterprise developers typically build, such as SQL database frontends, forms-based workflow, data visualization applications, and the like.

    And then from the JDIC project page:

    The JDesktop Integration Components (JDIC) project aims to make Java(TM) technology-based applications ("Java applications") first-class citizens of current desktop platforms without sacrificing platform independence.

    The quote is misleading because it doesn't explain how ActiveX is similar to JDNC/JDIC. The similarity is platform lock-in: ActiveX and COM means you're stuck on Windows (albeit with a choice of programming languages). JDNC/JDIC means you're stuck on Java (but without real, viable choice on the language).

    The fundamental problem (IMHO) is that desktop component integration is limited to a single desktop. Yes, I can have code reuse on Windows, and I can have code reuse on Gnome|KDE|Sun(tm)Java(r)Desktop(tm), but will I ever have (or need?) component integration across the three? It seems to me that developers have enough to handle getting the core functionality right.

    This kind of thing seems like just so much... distraction.

    1. Re:Not Quite by Decaff · · Score: 4, Insightful

      JDNC/JDIC means you're stuck on Java (but without real, viable choice on the language).

      Well, considering how widely used Java is, its a lot better than being stuck on Windows.

      Anyway, who says you are stuck with Java? There are dozens of languages available on the Java VM, including Python, LISP, Basic, Prolog, Smalltalk, Groovy, Ada, Forth, Pascal, Modula-2, Oberon and COBOL.

      The fundamental problem (IMHO) is that desktop component integration is limited to a single desktop.

      It isn't. Just because its using code from a library labelled 'jdesktop' does not mean that it is in any way restricted to Java Desktop - if you read about it you will see it will work with any Java client system - application, Applet, or WebStart, on any platform.

      but will I ever have (or need?) component integration across the three?

      You have it automatically, as the system is portable.

    2. Re:Not Quite by pnatural · · Score: 2, Insightful

      Well, considering how widely used Java is, its a lot better than being stuck on Windows.

      Since windows is more widely used than Java, by your argument, it's even better to be stuck on Windows. Ugh.

      Anyway, who says you are stuck with Java? There are dozens of languages available on the Java VM, including Python, LISP, Basic, Prolog, Smalltalk, Groovy, Ada, Forth, Pascal, Modula-2, Oberon and COBOL.

      I said "real, viable choice on the language". Are any of these real and viable? Not a troll, I'm curious: which of these is usable for enterprise or carrier-class applications? For which of them can I purchase a support contract from a reputable company?

      Just because its using code from a library labelled 'jdesktop' does not mean that it is in any way restricted to Java Desktop - if you read about it you will see it will work with any Java client system - application, Applet, or WebStart, on any platform.

      Oh, I see. It will work on any platform as long as that platform is Java. Got it.

    3. Re:Not Quite by Decaff · · Score: 2, Informative

      Since windows is more widely used than Java, by your argument, it's even better to be stuck on Windows. Ugh

      I was questioning your use of the word 'viable'. I mean, its like questioning if Windows is a viable desktop system. You may not like it (I don't) but there is no questioning that it is viable.

      I said "real, viable choice on the language". Are any of these real and viable?

      Most, if not all of them. Java Python (Jython) has a good solid history, and Groovy has a lot of momentum. The Smalltalks aren't that great, but work as command-line. There is a lot of interest in porting languages to the JVM, as its so widely available.

      Not a troll, I'm curious: which of these is usable for enterprise or carrier-class applications? For which of them can I purchase a support contract from a reputable company?

      Lots of them. For example, there are commercial and fully-supported compilers for COBOL, Pascal, Modula and Oberon.

      Others are open-source efforts.

      Oh, I see. It will work on any platform as long as that platform is Java. Got it.

      You asked if it was limited to a particular Desktop, not platform, didn't you?

  2. Oh GAWD. Just what we ALWAYS wanted. by sulli · · Score: 4, Funny

    Cross platform viruses, worms, spambots, and spyware? No thanks!

    --

    sulli
    RTFJ.
  3. Re:Oh GAWD. Just what we ALWAYS wanted. by Decaff · · Score: 2, Informative

    Er no. This is Java. Unlike ActiveX, its designed not to do nasty things.

  4. repeat after me - Java is *not* cross platform by DrSkwid · · Score: 2, Insightful

    It may have a few platforms but ubiquitous it isn't.

    It is like saying that Flash / Shockwave is cross platform just because there are a few players.

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    1. Re:repeat after me - Java is *not* cross platform by Decaff · · Score: 3, Insightful

      It may have a few platforms but ubiquitous it isn't

      Java is on at least Windows, .Net, MacOS, MacOS/X, Linux 32-bit, Linux 64-bit, BSD, OS/2 (yes, OS/2!), PalmOS, DG/UX, Tru64, OpenVMS, Reliant Unix, BS2000, HP-UX, Solaris, AIX, OS/390, OS/400, VM/ESA, Netware, Oracle embedded, DYNIX, Irix, Symbian, QNX, VxWorks, NextStep, OpenStep, OSF/1, DOS, AtheOS, RISC OS, ARMLinux, EPOC, GCOS, Windows CE, Psion Series 5, Plan 9, Sony Playstation (!).

      How would you define 'few'?

      but ubiquitous it isn't.

      Java is pre-installed on 60-70% of all new PCs. The number of JRE kits manually downloaded from Sun's site alone is in the tens of millions. There are well over a 100,000,000 mobile phones out there with embedded java.

      How would you define 'ubiquitous'?

  5. interesting by 12357bd · · Score: 2, Interesting

    Thing are getting interesting,
    Sun is approaching java to desktop (hurray for them, it only took 5 years!).
    Mac is publishing rendezvous for linux, win and others (after ten years of networking, will we finally get something like a 'zero' config system!?).

    It seems that the non-windows side of the world is awakening!.

    --
    What's in a sig?
  6. Re:Sun got it right... after someone shown the way by Decaff · · Score: 2, Interesting

    JDIC sounds like Sun has finally gave up "100% pure Java" principle and allows Java developers to access native functionality easily.

    You always have been able to do this. Its called JNI (Java Native Interface).

    It totally ignores all UI provided by client OS

    No it doesn't. You can cut and paste between Swing and the client OS. You can drag and drop between Swing and and client OS. You can access Client OS information, and Client OS Print Services. There are tools available that allow you to embed ActiveX components in Swing.

    which means that text boxes and file dialogs never behave correctly in Swing.

    Never behave correctly? I can enter text, cut, copy, paste, reformat, edit styled text and HTML.

    The file dialogs allow me to search for files and directories, filter by file types, create new directories.

    How is this not 'behaving correctly'?

    This is why SWT reacts 3x quicker than Swing

    Yes, SWT is a good product. However, the next release of Java (out September) allows Swing to be accelerated through the use of OpenGL. That should be fast.