Bug 869202
Summary: | Errai bus helloworld demo - possible problem with *.gwt.xml module file | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] JBoss Enterprise WFK Platform 2 | Reporter: | Stefan Miklosovic <smikloso> | ||||
Component: | Examples, Errai | Assignee: | Pavel SLegr <pslegr> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Stefan Miklosovic <smikloso> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 2.1.0 | CC: | bsutter, mnovotny, myarboro, oskutka, rruss | ||||
Target Milestone: | CR2 | ||||||
Target Release: | 2.1.0 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | errai-example | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2012-11-30 15:34:09 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
pslegr: please add CCFR for WFK 2.1 release notes known issue. the fix is very simple, rather fixed than creating known issue http://git.app.eng.bos.redhat.com/?p=errai/errai.git;a=commit;h=62da5898137c7c46a4e705d4fdcd42837b790dc0 I am verifying the fix resolved this issue. Distributed as a part of WFK 2.1.0.GA release. |
Created attachment 631981 [details] The error which appears directly after an user visits the application's entry page Description of problem: After successful depolying of the helloworld demo for Errai bus in the Errai example distribution, an user is confronted with the error message which he is required to cancel in order to proceed to the application itself (which works properly) Version-Release number of selected component (if applicable): jboss-wfk-2.1.0.ER2/demo/errai-2.1.0.Final-redhat-1/bus-examples/helloworld How reproducible: I was able to reproduce it on Firefox 16.0.1. It might be a case this bug is not present at the Safari. This information can be easily implied from the error message displayed to an user. Steps to Reproduce: 1. Deploy the application 2. Use it with firefox 3. See the error Actual results: Error message is displayed to the user. Expected results: The opposite of the actual results. Additional info: Please see the attachment in order to see the screenshot with the error message.