Topic
  • 6 replies
  • Latest Post - ‏2003-04-14T15:55:40Z by SystemAdmin
SystemAdmin
SystemAdmin
9394 Posts

Pinned topic what a headless exception!

‏2003-04-14T11:35:46Z |
When building(!) and packaging my app for the PocketPC I get the
following error:

IVE0027(W) In method MyApp$1/<init> (LMyApp;ljava/lang/String;)V,
thrown exception class java.awt.HeadlessException not found.


What the heck is a "HeadlessExcepation" and who throws or defines
this???

Michael
Updated on 2003-04-14T15:55:40Z at 2003-04-14T15:55:40Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    9394 Posts

    Re: what a headless exception!

    ‏2003-04-14T12:40:13Z  
    "Michael Moser" <mmo@zurich.ibm.com> wrote in message
    news:b7e692$3eiu$1@news.boulder.ibm.com...
    > When building(!) and packaging my app for the PocketPC I get the...

    To make this more precise: This is during generation of the .jxe file:

    ...
    IVEL0009(A) Loaded 689 class(es) in 15 seconds.
    IVEL0049(A) Reduced to 568 class(es) in 2 seconds.
    IVEL0027(W) In method MyApp$1/<init>(MyApp;Ljava/lang/String;)V,
    thrown exception class java.awt.HeadlessException not found.
    IVEL0012(A) Generated "E:\JavaDevt\MyApp.jxe" in 4 seconds.
    IVEL0036(A) Summary: 0 error(s), 2 warning(s), 689 class(es) read, 568
    class(es) written, 4 resource(s) written.
    IVEL0039(A) Summary: classes and resources require 907137 bytes ROM,
    368256(no JIT)/450752(JIT) bytes RAM.


  • SystemAdmin
    SystemAdmin
    9394 Posts

    Re: what a headless exception!

    ‏2003-04-14T12:49:22Z  
    "Michael Moser" <mmo@zurich.ibm.com> wrote in message
    news:b7e692$3eiu$1@news.boulder.ibm.com...
    > When building(!) and packaging my app for the PocketPC I get the...

    To make this more precise: This is during generation of the .jxe file:

    ...
    IVEL0009(A) Loaded 689 class(es) in 15 seconds.
    IVEL0049(A) Reduced to 568 class(es) in 2 seconds.
    IVEL0027(W) In method MyApp$1/<init>(MyApp;Ljava/lang/String;)V,
    thrown exception class java.awt.HeadlessException not found.
    IVEL0012(A) Generated "E:\JavaDevt\MyApp.jxe" in 4 seconds.
    IVEL0036(A) Summary: 0 error(s), 2 warning(s), 689 class(es) read, 568
    class(es) written, 4 resource(s) written.
    IVEL0039(A) Summary: classes and resources require 907137 bytes ROM,
    368256(no JIT)/450752(JIT) bytes RAM.


    java.awt. HeadlessExcepation is introduced in JDK 1.4. J9 is JDK 1.3
    compatible

    Have you eventually used JDK 1.4 compatible compiler?


    Vasil Panushev
    QA Embedded Technologies department

    ProSyst Bulgaria, Inc.
    48 Vladajska Str. Sofia, Bulgaria,
    Tel. (+359 2) 952 35 81
    http://www.prosyst.com v_panushev@prosyst.bg

    Leading Software Technology for Open Service Gateways

    "Michael Moser" <mmo@zurich.ibm.com> wrote in message
    news:b7ea1t$3mci$1@news.boulder.ibm.com...
    > "Michael Moser" <mmo@zurich.ibm.com> wrote in message
    > news:b7e692$3eiu$1@news.boulder.ibm.com...
    > > When building(!) and packaging my app for the PocketPC I get the...
    >
    > To make this more precise: This is during generation of the .jxe file:
    >
    > ...
    > IVEL0009(A) Loaded 689 class(es) in 15 seconds.
    > IVEL0049(A) Reduced to 568 class(es) in 2 seconds.
    > IVEL0027(W) In method MyApp$1/<init>(MyApp;Ljava/lang/String;)V,
    > thrown exception class java.awt.HeadlessException not found.
    > IVEL0012(A) Generated "E:\JavaDevt\MyApp.jxe" in 4 seconds.
    > IVEL0036(A) Summary: 0 error(s), 2 warning(s), 689 class(es) read, 568
    > class(es) written, 4 resource(s) written.
    > IVEL0039(A) Summary: classes and resources require 907137 bytes ROM,
    > 368256(no JIT)/450752(JIT) bytes RAM.
    >
    >

  • SystemAdmin
    SystemAdmin
    9394 Posts

    Re: what a headless exception!

    ‏2003-04-14T14:10:31Z  
    "Michael Moser" <mmo@zurich.ibm.com> wrote in message
    news:b7e692$3eiu$1@news.boulder.ibm.com...
    > When building(!) and packaging my app for the PocketPC I get the...

    To make this more precise: This is during generation of the .jxe file:

    ...
    IVEL0009(A) Loaded 689 class(es) in 15 seconds.
    IVEL0049(A) Reduced to 568 class(es) in 2 seconds.
    IVEL0027(W) In method MyApp$1/<init>(MyApp;Ljava/lang/String;)V,
    thrown exception class java.awt.HeadlessException not found.
    IVEL0012(A) Generated "E:\JavaDevt\MyApp.jxe" in 4 seconds.
    IVEL0036(A) Summary: 0 error(s), 2 warning(s), 689 class(es) read, 568
    class(es) written, 4 resource(s) written.
    IVEL0039(A) Summary: classes and resources require 907137 bytes ROM,
    368256(no JIT)/450752(JIT) bytes RAM.


    This is quite odd since we don't ship a java.awt.HeadlessException class
    with our AWT runtimes. Perhaps you have JDK 1.4 stuff on your classpath?

    David

    "Michael Moser" <mmo@zurich.ibm.com> wrote in message
    news:b7ea1t$3mci$1@news.boulder.ibm.com...
    > "Michael Moser" <mmo@zurich.ibm.com> wrote in message
    > news:b7e692$3eiu$1@news.boulder.ibm.com...
    > > When building(!) and packaging my app for the PocketPC I get the...
    >
    > To make this more precise: This is during generation of the .jxe file:
    >
    > ...
    > IVEL0009(A) Loaded 689 class(es) in 15 seconds.
    > IVEL0049(A) Reduced to 568 class(es) in 2 seconds.
    > IVEL0027(W) In method MyApp$1/<init>(MyApp;Ljava/lang/String;)V,
    > thrown exception class java.awt.HeadlessException not found.
    > IVEL0012(A) Generated "E:\JavaDevt\MyApp.jxe" in 4 seconds.
    > IVEL0036(A) Summary: 0 error(s), 2 warning(s), 689 class(es) read, 568
    > class(es) written, 4 resource(s) written.
    > IVEL0039(A) Summary: classes and resources require 907137 bytes ROM,
    > 368256(no JIT)/450752(JIT) bytes RAM.
    >
    >

  • SystemAdmin
    SystemAdmin
    9394 Posts

    Re: what a headless exception!

    ‏2003-04-14T15:12:57Z  
    This is quite odd since we don't ship a java.awt.HeadlessException class
    with our AWT runtimes. Perhaps you have JDK 1.4 stuff on your classpath?

    David

    "Michael Moser" <mmo@zurich.ibm.com> wrote in message
    news:b7ea1t$3mci$1@news.boulder.ibm.com...
    > "Michael Moser" <mmo@zurich.ibm.com> wrote in message
    > news:b7e692$3eiu$1@news.boulder.ibm.com...
    > > When building(!) and packaging my app for the PocketPC I get the...
    >
    > To make this more precise: This is during generation of the .jxe file:
    >
    > ...
    > IVEL0009(A) Loaded 689 class(es) in 15 seconds.
    > IVEL0049(A) Reduced to 568 class(es) in 2 seconds.
    > IVEL0027(W) In method MyApp$1/<init>(MyApp;Ljava/lang/String;)V,
    > thrown exception class java.awt.HeadlessException not found.
    > IVEL0012(A) Generated "E:\JavaDevt\MyApp.jxe" in 4 seconds.
    > IVEL0036(A) Summary: 0 error(s), 2 warning(s), 689 class(es) read, 568
    > class(es) written, 4 resource(s) written.
    > IVEL0039(A) Summary: classes and resources require 907137 bytes ROM,
    > 368256(no JIT)/450752(JIT) bytes RAM.
    >
    >

    "David Whiteman" <bogus@us.ibm.com> wrote in message
    news:b7efbe$2uki$1@news.boulder.ibm.com...
    > This is quite odd since we don't ship a java.awt.HeadlessException
    class
    > with our AWT runtimes. Perhaps you have JDK 1.4 stuff on your
    classpath?
    >
    > David

    While I have indeed a JDK1.4 installed, I am running WSDD using the J9
    that comes with it (on my system in E:\IBM\Device
    Developer\wsdd5.0\ive) and I am also using this environment to compile
    things (since I also want to use J9 to run the stuff on the PocketPC).
    At least the entry under Libraries reads "JRE System Library (Detected
    VM)." and under "Windows => Preferences => Java => Installed JREs"
    there is a line "J9 VM Detected VM E:\IBM\Device
    Developer\wsdd5.0\ive".

    So I would guess, it uses the J9 JRE for compilation as well as for
    the classpath and there is nothing that I am aware of that points to
    the JDK1.4 stuff.

    Strange...

    Michael

  • SystemAdmin
    SystemAdmin
    9394 Posts

    Re: what a headless exception!

    ‏2003-04-14T15:31:43Z  
    "David Whiteman" <bogus@us.ibm.com> wrote in message
    news:b7efbe$2uki$1@news.boulder.ibm.com...
    > This is quite odd since we don't ship a java.awt.HeadlessException
    class
    > with our AWT runtimes. Perhaps you have JDK 1.4 stuff on your
    classpath?
    >
    > David

    While I have indeed a JDK1.4 installed, I am running WSDD using the J9
    that comes with it (on my system in E:\IBM\Device
    Developer\wsdd5.0\ive) and I am also using this environment to compile
    things (since I also want to use J9 to run the stuff on the PocketPC).
    At least the entry under Libraries reads "JRE System Library (Detected
    VM)." and under "Windows => Preferences => Java => Installed JREs"
    there is a line "J9 VM Detected VM E:\IBM\Device
    Developer\wsdd5.0\ive".

    So I would guess, it uses the J9 JRE for compilation as well as for
    the classpath and there is nothing that I am aware of that points to
    the JDK1.4 stuff.

    Strange...

    Michael

    "Michael Moser" <mmo@zurich.ibm.com> wrote in message
    news:b7ej09$37gc$1@news.boulder.ibm.com...
    > While I have indeed a JDK1.4 installed, I am running WSDD using the J9
    > that comes with it (on my system in E:\IBM\Device
    > Developer\wsdd5.0\ive) and I am also using this environment to compile
    > things (since I also want to use J9 to run the stuff on the PocketPC).
    > At least the entry under Libraries reads "JRE System Library (Detected
    > VM)." and under "Windows => Preferences => Java => Installed JREs"
    > there is a line "J9 VM Detected VM E:\IBM\Device
    > Developer\wsdd5.0\ive".
    >
    > So I would guess, it uses the J9 JRE for compilation as well as for
    > the classpath and there is nothing that I am aware of that points to
    > the JDK1.4 stuff.

    This HeadlessException appears to be thrown from an anonymous inner class of
    a class named MyApp, which I presume is your code. Please check the source
    of MyApp.java to see if you can find text references to HeadlessException.

    > IVEL0027(W) In method MyApp$1/<init>(MyApp;Ljava/lang/String;)V,
    > thrown exception class java.awt.HeadlessException not found.

    David

  • SystemAdmin
    SystemAdmin
    9394 Posts

    Re: what a headless exception!

    ‏2003-04-14T15:55:40Z  
    "Michael Moser" <mmo@zurich.ibm.com> wrote in message
    news:b7ej09$37gc$1@news.boulder.ibm.com...
    > While I have indeed a JDK1.4 installed, I am running WSDD using the J9
    > that comes with it (on my system in E:\IBM\Device
    > Developer\wsdd5.0\ive) and I am also using this environment to compile
    > things (since I also want to use J9 to run the stuff on the PocketPC).
    > At least the entry under Libraries reads "JRE System Library (Detected
    > VM)." and under "Windows => Preferences => Java => Installed JREs"
    > there is a line "J9 VM Detected VM E:\IBM\Device
    > Developer\wsdd5.0\ive".
    >
    > So I would guess, it uses the J9 JRE for compilation as well as for
    > the classpath and there is nothing that I am aware of that points to
    > the JDK1.4 stuff.

    This HeadlessException appears to be thrown from an anonymous inner class of
    a class named MyApp, which I presume is your code. Please check the source
    of MyApp.java to see if you can find text references to HeadlessException.

    > IVEL0027(W) In method MyApp$1/<init>(MyApp;Ljava/lang/String;)V,
    > thrown exception class java.awt.HeadlessException not found.

    David


    "David Whiteman" <bogus@us.ibm.com> wrote in message
    news:b7ek3m$2lfu$1@news.boulder.ibm.com...
    > "Michael Moser" <mmo@zurich.ibm.com> wrote in message
    > news:b7ej09$37gc$1@news.boulder.ibm.com...
    > > ...
    > This HeadlessException appears to be thrown from an anonymous inner
    class of
    > a class named MyApp, which I presume is your code. Please check the
    source
    > of MyApp.java to see if you can find text references to
    HeadlessException.

    I think it actually might have had to do with the fact that I was
    still occasionally using "standard eclipse" (which was set to use
    JDK1.4) and that a "rebuild all" there may have caused it to recompile
    classes which it should no longer touch (since I am using these with
    WSDD now). I switched eclipse to J9 as well - so in case this happens
    again, it should not cause such harm any more.

    Sorry for the inconvenience.

    Michael