Menu

#246 ASM-based portlet doesn't work with guse 3.7

3.6.2
open
ASM (4)
9 - High
2015-01-12
2014-12-14
No

Dear Developer,

Recently I upgraded my gateway from guse-3.6.8 to guse-3.7 . However I found out that my ASM-based application portlets doesn't work properly with guse-3.7.

This is the error message that I got:

11:41:36.649 [ajp-bio-8009-exec-8] DEBUG h.s.l.p.portlets.GVATA.GVATAPortlet - hu.sztaki.lpds.pgportal.portlets.GVATA.GVATAPortlet.(javax.portlet.ActionRequest, javax.portlet.ActionResponse)

It seems that when the html form send the post variable to the $pURL address, the liferay wasn't responding/follow up the request. Perhaps is there any workaround to solve this issue?

Regards

Related

Bugs: #246

Discussion

  • Akos Balasko

    Akos Balasko - 2014-12-16

    Dear Farhan,

    This happens because of the newest version of gUSE supports Liferay 6.2 in where mayor modifications has been put in force in the field of client-server parameter passing.

    See: http://stackoverflow.com/questions/20989498/form-data-in-request-is-null-when-using-actionmapping-requestmapping-in-liferay

    So you need to change liferay-portlet.xml by adding <requires-namespaced-parameters>false</requires-namespaced-parameters> row in <portlet> tag.</portlet>

    Moreover please be sure that the following tag is not placed neither in liferay-display.xml nor liferay-portlet.xml:

    <!DOCTYPE liferay-portlet-app PUBLIC "-//Liferay//DTD Portlet Application 6.1.0//EN" "http://www.liferay.com/dtd/liferay-portlet-app_6_1_0.dtd">

    (This line avoids to deploy your web application to Liferay 6.2)

    Cheers,

    akos

     

    Last edit: Akos Balasko 2014-12-17
    • Muhammad Farhan Sjaugi

      Dear Akos,

      Thank you for the information. Btw, which tag that should I avoid?

      On Tue, Dec 16, 2014 at 8:11 PM, Akos Balasko akosbalasko@users.sf.net
      wrote:

      Dear Farhan,

      This happens because of the newest version of gUSE supports Liferay 6.2 in
      where mayor modifications has been put in force in the field of
      client-server parameter passing.

      See:
      http://stackoverflow.com/questions/20989498/form-data-in-request-is-null-when-using-actionmapping-requestmapping-in-liferay

      So you need to change liferay-portlet.xml by adding
      <requires-namespaced-parameters>false</requires-namespaced-parameters> row
      in <portlet> tag.</portlet>

      Moreover please be sure that the following tag is not placed neither in
      liferay-display.xml nor liferay-portlet.xml:

      (This line avoids to deploy your web application to Liferay 6.2)

      Cheers,

      akos

      Status: open
      Group: 3.6.2
      Labels: ASM
      Created: Sun Dec 14, 2014 08:47 AM UTC by Muhammad Farhan Sjaugi
      Last Updated: Sun Dec 14, 2014 08:47 AM UTC
      Owner: nobody

      Dear Developer,

      Recently I upgraded my gateway from guse-3.6.8 to guse-3.7 . However I
      found out that my ASM-based application portlets doesn't work properly with
      guse-3.7.

      This is the error message that I got:

      11:41:36.649 [ajp-bio-8009-exec-8] DEBUG
      h.s.l.p.portlets.GVATA.GVATAPortlet -
      hu.sztaki.lpds.pgportal.portlets.GVATA.GVATAPortlet.(javax.portlet.ActionRequest,
      javax.portlet.ActionResponse)

      It seems that when the html form send the post variable to the $pURL
      address, the liferay wasn't responding/follow up the request. Perhaps is
      there any workaround to solve this issue?

      Regards

      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/guse/bugs/246/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

      --
      Muhammad Farhan Sjaugi, S.Kom. M.Sc
      email: fhn@cbcommunity.or.id

       

      Related

      Bugs: #246

  • Akos Balasko

    Akos Balasko - 2014-12-17

    Sorry, the Sourceforge has resolved the html tags :)
    I updated my first answer.

    Cheers,
    akos

     
    • Muhammad Farhan Sjaugi

      Dear Akos,

      Thanks for your reply. In my implementation, I update the 6_1 value to 6_2
      instead of remove tag.

      Anyway, I also notice that the configuration page to set the workflow is
      also not functioning well. This is the error message that I got:

      15:55:09,675 ERROR [http-bio-8080-exec-1][render_portlet_jsp:132] null
      java.lang.ArrayIndexOutOfBoundsException: 1
      at
      hu.sztaki.lpds.pgportal.portlets.GVATA.GVATAConfiguration.processAction(GVATAConfiguration.java:55)
      at
      com.liferay.portal.kernel.bean.ClassLoaderBeanHandler.invoke(ClassLoaderBeanHandler.java:67)
      at
      com.liferay.portlet.portletconfiguration.action.EditConfigurationAction.processAction(EditConfigurationAction.java:76)
      at
      com.liferay.portal.struts.PortletRequestProcessor.process(PortletRequestProcessor.java:166)
      at
      com.liferay.portlet.StrutsPortlet.processAction(StrutsPortlet.java:216)
      at com.liferay.portlet.FilterChainImpl.doFilter(FilterChainImpl.java:71)
      at
      com.liferay.portal.kernel.portlet.PortletFilterUtil.doFilter(PortletFilterUtil.java:48)
      at
      com.liferay.portlet.InvokerPortletImpl.invoke(InvokerPortletImpl.java:618)
      at
      com.liferay.portlet.InvokerPortletImpl.invokeAction(InvokerPortletImpl.java:649)
      at
      com.liferay.portlet.InvokerPortletImpl.processAction(InvokerPortletImpl.java:312)
      at
      com.liferay.portlet.PortletContainerImpl._doProcessAction(PortletContainerImpl.java:402)
      at
      com.liferay.portlet.PortletContainerImpl.processAction(PortletContainerImpl.java:110)
      at
      com.liferay.portlet.SecurityPortletContainerWrapper.processAction(SecurityPortletContainerWrapper.java:109)
      at
      com.liferay.portlet.RestrictPortletContainerWrapper.processAction(RestrictPortletContainerWrapper.java:75)
      at
      com.liferay.portal.kernel.portlet.PortletContainerUtil.processAction(PortletContainerUtil.java:115)
      at
      com.liferay.portal.action.LayoutAction.processLayout(LayoutAction.java:356)
      at
      com.liferay.portal.action.LayoutAction.doExecute(LayoutAction.java:178)
      at com.liferay.portal.action.LayoutAction.execute(LayoutAction.java:79)
      at
      org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
      at
      org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)

      Any idea how to solve this?

      Regards

      On Wed, Dec 17, 2014 at 8:52 PM, Akos Balasko akosbalasko@users.sf.net
      wrote:

      Sorry, the Sourceforge has resolved the html tags :)
      I updated my first answer.

      Cheers,
      akos


      Status: open
      Group: 3.6.2
      Labels: ASM
      Created: Sun Dec 14, 2014 08:47 AM UTC by Muhammad Farhan Sjaugi
      Last Updated: Tue Dec 16, 2014 12:11 PM UTC
      Owner: nobody

      Dear Developer,

      Recently I upgraded my gateway from guse-3.6.8 to guse-3.7 . However I
      found out that my ASM-based application portlets doesn't work properly with
      guse-3.7.

      This is the error message that I got:

      11:41:36.649 [ajp-bio-8009-exec-8] DEBUG
      h.s.l.p.portlets.GVATA.GVATAPortlet -
      hu.sztaki.lpds.pgportal.portlets.GVATA.GVATAPortlet.(javax.portlet.ActionRequest,
      javax.portlet.ActionResponse)

      It seems that when the html form send the post variable to the $pURL
      address, the liferay wasn't responding/follow up the request. Perhaps is
      there any workaround to solve this issue?

      Regards

      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/guse/bugs/246/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

      --
      Muhammad Farhan Sjaugi, S.Kom. M.Sc
      email: fhn@cbcommunity.or.id

       

      Related

      Bugs: #246

  • Gabor Hermann

    Gabor Hermann - 2015-01-12
    • assigned_to: Akos Balasko
     

Log in to post a comment.