掲示板

FileUpload causes error on Ajax requests of another portlets on same page

10年前 に Pablo Díez によって更新されました。

FileUpload causes error on Ajax requests of another portlets on same page

New Member 投稿: 2 参加年月日: 13/09/30 最新の投稿
Hi all,

I found a strange behavior when using the FileUpload component with multiple portlets on the same page using PrimeFaces on Liferay and Liferay Bridge.

When I put two portlet instances PrimeFaces3 on the same page, and upload a file from the first portlet instance, I can't upload a file from the second portlet instance or Ajax requests correctly (eg. dataTable update). No exceptions were thrown.

I obtained the same results using:
- A custom portlet that uses FileUpload and another not.
- Two custom portlets using FileUpload.

Using Liferay Faces Bridge 3.1.1-GA2 I got HTTP 400 response to Ajax requests from the second instance.
Using Liferay Faces Bridge 3.1.3-GA4 I got HTTP 200 response to Ajax requests from the second instance, but still failing.

Any help is appreciated.

My environment is:

Liferay 6.1.1 CE GA2
PrimeFaces 3.5
Liferay Faces Bridge 3.1.1-GA2 / 3.1.3-GA4

BR,

Pablo
thumbnail
10年前 に Kyle Joseph Stiemann によって更新されました。

RE: FileUpload causes error on Ajax requests of another portlets on same pa

Liferay Master 投稿: 760 参加年月日: 13/01/14 最新の投稿
Hi Pablo,
I think you may be experiencing FACES-1384. Please let me know if you think your issue is related.

- Kyle
10年前 に Pablo Díez によって更新されました。

RE: FileUpload causes error on Ajax requests of another portlets on same pa

New Member 投稿: 2 参加年月日: 13/09/30 最新の投稿
Hi Kyle,

You are right. Thanks for the issue link and your help. Are there any estimation for the resolution of this issue?

Anyway, do u know some workaround to fix it? Thanks in advance.

Pablo.
thumbnail
10年前 に Kyle Joseph Stiemann によって更新されました。

RE: FileUpload causes error on Ajax requests of another portlets on same pa

Liferay Master 投稿: 760 参加年月日: 13/01/14 最新の投稿
Unfortunately, there is no known workaround. Please vote for the related Primefaces Issue if you would like to see this fixed.

Thanks,
- Kyle