Bug 781056 (SOA-3542) - BPEL web console doesn't work properly on Internet Explorer 7,8 - on Win2k3
Summary: BPEL web console doesn't work properly on Internet Explorer 7,8 - on Win2k3
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: SOA-3542
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Documentation
Version: 5.2.0.ER6
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ER2
: 5.3.0 GA
Assignee: David Le Sage
QA Contact: ecs-bugs
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-01 15:28 UTC by Robert Balent
Modified: 2014-01-13 00:20 UTC (History)
7 users (show)

Fixed In Version: 5.3.0 GA
Doc Type: Bug Fix
Doc Text:
The BPEL web console does not work with Internet Explorer 7 and 8 on Windows 2003. As a workaround, please use the Mozilla Firefox browser in this environment instead.
Clone Of:
Environment:
Last Closed: 2012-07-31 05:47:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-3542 0 Critical Closed BPEL web console doesn't work properly on Internet Explorer 7,8 2015-07-21 10:40:45 UTC

Description Robert Balent 2011-11-01 15:28:43 UTC
Workaround Description: Robert - does Firefox work on Windows?
project_key: SOA

When you try to open BPEL web console in Internet Explorer 7 and 8, only loading bar is showed.

Comment 1 Len DiMaggio 2011-11-01 15:33:24 UTC
Workaround Description: Added: Robert - does Firefox work on Windows?


Comment 2 Ivo Bek 2011-11-01 15:34:49 UTC
Link: Added: This issue depends RIFTSAW-460


Comment 3 Robert Balent 2011-11-01 15:35:12 UTC
Len: Firefox works properly on windows.

Comment 4 Jeff Yu 2011-11-02 00:20:30 UTC
Hi Robert,

I've tried the SOA-5.2.0.ER5, deployed in my local Mac OSX machine, and then use both IE7 & IE9, they are working fine. (although the layout and font are not as beautiful as Firefox/Chrome), I am interested in that whether you also deployed the SOA under windows? I've tested it in two windows7 machine.

Comment 5 (please assign to mrietvel@redhat.com) 2011-11-02 12:18:29 UTC
Link: Added: This issue Cloned to JBPM-3424


Comment 6 (please assign to mrietvel@redhat.com) 2011-11-02 12:20:54 UTC
Link: Removed: This issue Cloned to JBPM-3424 


Comment 7 Robert Balent 2011-11-02 14:47:08 UTC
Hi Jeff,

I tried with SOA platform deployed on linux and windows machine too. I've reproduced it on our lab machines soa5 and soa7.

Comment 8 Jiri Pechanec 2011-11-03 09:16:40 UTC
I tried it at home - Windows XP/IE 8 - works for me

Comment 9 Jeff Yu 2011-11-03 09:32:03 UTC
I downloaded the SOA-P ER6 today, and tried it again with Windows7/IE7, works fine.

Comment 10 Jeff Yu 2011-11-04 09:19:36 UTC
So here is the summary for this issue.

The web console doesn't work against the IE7/IE8 under Win2k3, however, it works fine on the IE7/IE9 under Windows7 and the IE8 under Windows XP. (This is based on Ivo, Robert, Jiri and myself test), For the specific IE7/IE8 under Win2k3, it can be workaround by using Firefox on Win2k3. I would suggest that we add this into the release note by saying use Firefox for users under Win2k3. In next release, when we upgrade the GWT version, this issue might be gone. It is a bit hard to debug this issue at this late stage.

Regards
Jeff

Comment 11 Len DiMaggio 2012-05-10 17:15:12 UTC
This: Windows 2003 x86_64

Is still a supported configuration - see: https://docspace.corp.redhat.com/docs/DOC-85222

If we're not going to support IE on Win2k3, then we need to document this as a limitation.

Comment 12 David Le Sage 2012-05-15 04:46:07 UTC
We will document this as a known issue in the release notes.

Comment 13 David Le Sage 2012-07-02 05:13:58 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
The BPEL web console does not work with Internet Explorer 7 and 8 on Windows 2003. As a workaround, please use the Mozilla Firefox browser in this environment instead.


Note You need to log in before you can comment on or make changes to this bug.