I was unsuccesful to repeat your issue. For me, deployment and building of the demo and its functionality is not affected by any way and the demo as such works properly. Maybe your local settings are different from mine. In that case, please write down version of software, jdk and so on.

java version "1.7.0_09-icedtea"
OpenJDK Runtime Environment (fedora-2.3.8.0.fc17-x86_64)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)

javac 1.7.0_09

Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)

JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4)

Firefox 19.0

Same configuration except java and javac. With openJDK & javac 1.7.0_09

java version "1.7.0_09-icedtea"
OpenJDK Runtime Environment (fedora-2.3.4.fc17-x86_64)
OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode)

works properly.

With Oracle java & javac 1.7.0_09

java version "1.7.0_09"
Java(TM) SE Runtime Environment (build 1.7.0_09-b05)
Java HotSpot(TM) 64-Bit Server VM (build 23.5-b02, mixed mode)

not working.

We've just had a report of this same problem from one of our community members. His Java version info:

java version "1.7.0_15"
OpenJDK Runtime Environment (IcedTea7 2.3.7) (7u15-2.3.7-0ubuntu1~12.10.1)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)

This leads me to believe the problem is going to exist in javac of all the newer releases of JDK 7 and OpenJDK 7. :-(

Works with

java version "1.6.0_37"
Java(TM) SE Runtime Environment (build 1.6.0_37-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01, mixed mode)

More digging tomorrow.

Here's some more info from our community:

https://community.jboss.org/thread/200433?tstart=0 -- Same issue reported against Oracle JDK 7u4

https://issues.jboss.org/browse/ERRAI-311 -- Same issue reported against Oracle JDK 7u3

I've just created a new Fedora VM to try this out on. The build passes on the latest available Oracle JDK:

Java version: 1.7.0_17, vendor: Oracle Corporation
Java home: /home/jfuerth/jdk1.7.0_17/jre

But fails on OpenJDK:

Java version: 1.7.0_09-icedtea, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.9.x86_64/jre

Note that this is the opposite result that Emil reported in comment 2! :-/

The build also passes on OpenJDK 1.7.0_09 if I force the demo to build with GWT 2.5.1 rather than 2.4.0 by adding the following within the <dependencyManagement> section of pom.xml:

      <dependency>
        <groupId>com.google.gwt</groupId>
        <artifactId>gwt-user</artifactId>
        <version>2.5.1</version>
      </dependency>

      <dependency>
        <groupId>com.google.gwt</groupId>
        <artifactId>gwt-dev</artifactId>
        <version>2.5.1</version>
      </dependency>

Despite this, I'm unable to find any information in GWT's own bug tracker about this problem or its resolution.

In any case, we're now satisfied from an upstream project point of view because we have plenty of verified workarounds: use Oracle JDK 7u17, work with GWT 2.5.x, or switch to the Errai 2.3 or 3.0 branches.

Workaround verified for latest Oracle java 1.7.0_17-b02 + GWT 2.4.0
and latest openJDK 1.7.0_09-icedtea(2.3.8) + GWT 2.5.0

comment 2 note: I built project with Oracle java 1.7.0_09 and run with openJDK 1.7.0_09 (2.3.4). Build passes with latest openJDK 2.3.8 (but error still present with GWT 2.4.0).

Jonathan, Emil returned back to ASSIGNED. We either need to deliver the workaround in the archetype or to have a release note.

Any one of the following will resolve the issue. Which is preferable?

1. Use Errai 2.3 (in the pipeline for WFK 2.3)
2. Force Errai 2.2 (in WFK 2.2) onto GWT 2.5.x
3. Strip Bean Validation out of the archetype when generating with -Denterprise=true
4. Document that the demo does not compile with OpenJDK 7 (but it does work with OpenJDK 6, Oracle JDK 6, Oracle JDK 7, IBM JDK 7)

Please advise.

Doc text added.

Modified Doc text based on Emil's testing results. Emil is about to provide a more detailed comment tomorrow.

I tested several JDKs again. Looks like compilation is successful on all OracleJDKs and validation works well when deployed on any version of OpenJDK. To prevent hitting some bad combination I suggested to note workaround as Peter did.

Jonathan, you comment was somehow buried. I personally prefer option 3., hopefully it represents the least work for you.

specified the failing Oracle JDK 7 version in the doc text more precisely:

earlier versions of Oracle JDK 7
>>
Oracle JDK 7 update 16 or earlier

doc text updated in RN book: https://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Web_Framework_Kit/2.2/html-single/2.2.0_Release_Notes/index.html

Migrated to JIRA

Jonathan Fuerth <jfuerth> made a comment on jira WFK2-40

Note that this issue only applies to GWT 2.4 projects, so it is no longer relevant to Errai 2.3.2 & WFK 2.3 since these now require use of GWT 2.5.1.

Marek Novotny <mnovotny> made a comment on jira WFK2-40

Clearing proposed Target Release value from 2.0.0.GA to Unknown

Rodney Russ <rruss> made a comment on jira WFK2-40

why not close the issue [~jfuerth] ?

Jonathan Fuerth <jfuerth> updated the status of jira WFK2-40 to Closed

Jonathan Fuerth <jfuerth> made a comment on jira WFK2-40

Only affects product branch.

Marek Novotny <mnovotny> made a comment on jira WFK2-40

The last comment is wrong. It affects only Errai 2.2.0 with used GWT 2.4.0

Marek Novotny <mnovotny> updated the status of jira WFK2-40 to Closed

Marek Novotny <mnovotny> updated the status of jira WFK2-40 to Reopened

Marek Novotny <mnovotny> made a comment on jira WFK2-40

reopening to fix the Fixed version

Matous Jobanek <mjobanek> updated the status of jira WFK2-40 to Reopened

Matous Jobanek <mjobanek> updated the status of jira WFK2-40 to Closed