Maven 2.x GWT Plugin

gwt:debug ends with java.lang.ClassFormatError with JEE 6

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.2
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    2

Description

GWT Shell ends with ClassFormatError after attaching a debugger to gwt:debug created JVM (JEE 6)

  1. Hosted.log
    29/Jan/10 7:53 AM
    6 kB
    Tim Lebedkov
  2. pom.xml
    29/Jan/10 7:57 AM
    5 kB
    Tim Lebedkov

Activity

Hide
Tim Lebedkov added a comment -

pom

Show
Tim Lebedkov added a comment - pom
Hide
James Gralton added a comment -

I have exactly the same issue. It is stopping me using dev/hosted mode as my war will eventually be deployed as part of a Java 6 Enterprise App on Glassfish v3. Is there likely to be a fix for this?

Show
James Gralton added a comment - I have exactly the same issue. It is stopping me using dev/hosted mode as my war will eventually be deployed as part of a Java 6 Enterprise App on Glassfish v3. Is there likely to be a fix for this?
Hide
nicolas de loof added a comment -

I wonder I can't see the "-noserver" option in your log.
Running server side on another server (beeing JavaEE6 or other) requires this option, or your JavaEE6 server classpath (servlet 3) will overlap with GWT hosted-server (servlet 2.5) that seems to be your case considering the ClassFormatError message

Show
nicolas de loof added a comment - I wonder I can't see the "-noserver" option in your log. Running server side on another server (beeing JavaEE6 or other) requires this option, or your JavaEE6 server classpath (servlet 3) will overlap with GWT hosted-server (servlet 2.5) that seems to be your case considering the ClassFormatError message

People

Vote (3)
Watch (0)

Dates

  • Created:
    Updated: