Uploaded image for project: 'PUBLIC - Liferay Faces'
  1. PUBLIC - Liferay Faces
  2. FACES-2913

bridge:inputFile fails to upload files in the jsf-cdi-applicant-portlet on Liferay 6.2

    Details

      Description

      Steps to Reproduce

      1. Start Liferay Portal 6.2

      2. Deploy the jsf-cdi-applicant-portlet from the 3.x branch of the liferay-faces-bridge-impl.git repository

      3. Add the jsf-cdi-portlet to a portal page

      4. View the portal page

      5. Click on the "Choose Files" button and select some files for uploading

      6. Click on the "Submit" button under the "Choose Files" button

      Expected Results:

      The files are uploaded and appear in the list.

      Actual Results:

      The files are not uploaded and do not appear in the list. On WebLogic, the portlet displays "jsf-cdi-applicant is temporarily unavailable" and the following error appears in the server log:

      java.lang.IllegalStateException: Unable to load current conversations from the associated request, something went badly wrong when associate() was called
      	at org.jboss.weld.context.AbstractConversationContext.getConversationMap(AbstractConversationContext.java:349)
      	at org.jboss.weld.context.AbstractConversationContext.deactivate(AbstractConversationContext.java:263)
      	at org.jboss.weld.servlet.WeldListener.requestDestroyed(WeldListener.java:130)
      	at org.jboss.weld.servlet.WeldCrossContextFilter.doFilter(WeldCrossContextFilter.java:66)
      	at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.processDoFilter(InvokerFilterChain.java:204)
      	at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.doFilter(InvokerFilterChain.java:109)
      	at com.liferay.cdi.portlet.bridge.CDICrossContextFilter.doFilter(CDICrossContextFilter.java:49)
      	at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.processDoFilter(InvokerFilterChain.java:204)
      	at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.doFilter(InvokerFilterChain.java:109)
      	at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilter.doFilter(InvokerFilter.java:119)
      	at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
      	at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
      	at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
      	at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:588)
      	at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:481)
      	at com.liferay.portlet.InvokerPortletImpl.invoke(InvokerPortletImpl.java:583)
      	at com.liferay.portlet.InvokerPortletImpl.invokeRender(InvokerPortletImpl.java:656)
      	at com.liferay.portlet.InvokerPortletImpl.render(InvokerPortletImpl.java:362)
      	at jsp_servlet._html._portal.__render_portlet._jspService(__render_portlet.java:1312)
      

        Activity

        Hide
        vernon.singleton Vernon Singleton added a comment - - edited

        Confirmed working with jsf2-cdi-portlet-3.2.5-ga6.war built with the glassfish profile, so marked this as a regression.

        Show
        vernon.singleton Vernon Singleton added a comment - - edited Confirmed working with jsf2-cdi-portlet-3.2.5-ga6.war built with the glassfish profile, so marked this as a regression.
        Hide
        vernon.singleton Vernon Singleton added a comment -

        Also confirmed that the bridge:inputFile component is working on liferay-portal-6.2.10-sp14-jsf-2.2-tomcat with the jsf-cdi-applicant portlet. So the issue is not affecting the bridge-impl-4.x branch.

        Show
        vernon.singleton Vernon Singleton added a comment - Also confirmed that the bridge:inputFile component is working on liferay-portal-6.2.10-sp14-jsf-2.2-tomcat with the jsf-cdi-applicant portlet. So the issue is not affecting the bridge-impl-4.x branch.
        Hide
        vernon.singleton Vernon Singleton added a comment -

        Also confirmed that the bridge:inputFile component is working on liferay-portal-6.2.10-sp15-jsf-2.2-tomcat with the jsf-cdi-applicant portlet. So the issue has nothing to do with sp15.

        Show
        vernon.singleton Vernon Singleton added a comment - Also confirmed that the bridge:inputFile component is working on liferay-portal-6.2.10-sp15-jsf-2.2-tomcat with the jsf-cdi-applicant portlet. So the issue has nothing to do with sp15.
        Hide
        kyle.stiemann Kyle Stiemann added a comment -

        This issue causes test failures:

        Failed tests:   runApplicantPortletTest_J_Submit(com.liferay.faces.bridge.test.integration.demo.applicant.JSF_CDIApplicantPortletTester): Element //form[@method='post'] does not contain text "Dear David,". Instead it contains text "Dear ,(..)
        
        Tests in error:
          runApplicantPortletTest_I_FileUpload(com.liferay.faces.bridge.test.integration.demo.applicant.JSF_CDIApplicantPortletTester): Timed out after 10 seconds waiting for visibility of element located by By.xpath: //tr[@class='portlet-section-body results-row']/td[2](..)
        
        Show
        kyle.stiemann Kyle Stiemann added a comment - This issue causes test failures: Failed tests: runApplicantPortletTest_J_Submit(com.liferay.faces.bridge.test.integration.demo.applicant.JSF_CDIApplicantPortletTester): Element //form[@method='post'] does not contain text "Dear David,". Instead it contains text "Dear ,(..) Tests in error: runApplicantPortletTest_I_FileUpload(com.liferay.faces.bridge.test.integration.demo.applicant.JSF_CDIApplicantPortletTester): Timed out after 10 seconds waiting for visibility of element located by By.xpath: //tr[@class='portlet-section-body results-row']/td[2](..)

          People

          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development

                Subcomponents