ICEmobile
  1. ICEmobile
  2. MOBI-805

Byte array and resouce backed audio not playing on WAS

          Details

          • Type: Bug Bug
          • Status: Resolved
          • Priority: Major Major
          • Resolution: Invalid
          • Affects Version/s: 1.3 Final
          • Fix Version/s: EE 1.3
          • Component/s: Faces
          • Labels:
            None
          • Environment:
            ICEmobile on WAS

            Description

            In mobileshowcase on WAS, byte array and resource backed audio clips will not play. Fixed url backed audio clips play fine. The problem also appeared in initial WebLogic testing.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Ted Goddard added a comment -

              ByteArray and Resource audio play back successfully on iPad Safari.

              Show
              Ted Goddard added a comment - ByteArray and Resource audio play back successfully on iPad Safari.
              Hide
              Permalink
              Ted Goddard added a comment -

              This is likely due to "Enable URL rewriting" not being configured for WebSphere.

              http://wiki.icesoft.com/display/ICEmobileEE/Websphere

              Show
              Ted Goddard added a comment - This is likely due to "Enable URL rewriting" not being configured for WebSphere. http://wiki.icesoft.com/display/ICEmobileEE/Websphere
              Hide
              Permalink
              Ted Goddard added a comment -

              URL rewriting has been enabled, but conflicting JSESSIONID in the URL and in the headers is preventing these resources from loading. It's possible that a change is WebSphere behavior resulted in this working in the past. It may be necessary to simply advise developers of applications deployed to WebSphere to use absolute URLs for audio and video clips.

              Show
              Ted Goddard added a comment - URL rewriting has been enabled, but conflicting JSESSIONID in the URL and in the headers is preventing these resources from loading. It's possible that a change is WebSphere behavior resulted in this working in the past. It may be necessary to simply advise developers of applications deployed to WebSphere to use absolute URLs for audio and video clips.
              Hide
              Permalink
              Ted Goddard added a comment -

              This can be resolved by rebooting the android device: the problem is that the media playback system may have acquired cookies from earlier sessions that have been invalidated and these cookies are not cleared when Chrome cookies are cleared.
              A user entering the application from a clean start will be able to play back the media. This has been verified on Nexus 7.

              Show
              Ted Goddard added a comment - This can be resolved by rebooting the android device: the problem is that the media playback system may have acquired cookies from earlier sessions that have been invalidated and these cookies are not cleared when Chrome cookies are cleared. A user entering the application from a clean start will be able to play back the media. This has been verified on Nexus 7.

                People

                • Assignee:
                  Ted Goddard
                  Reporter:
                  Steve Maryka
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: