[JBoss JIRA] Resolved: (GTNPORTAL-1834) Portlet's context-root cannot contain slashes
by Minh Hoang TO (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-1834?page=com.atlassian.jira.pl... ]
Minh Hoang TO resolved GTNPORTAL-1834.
--------------------------------------
Resolution: Done
> Portlet's context-root cannot contain slashes
> ---------------------------------------------
>
> Key: GTNPORTAL-1834
> URL: https://issues.jboss.org/browse/GTNPORTAL-1834
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Thomas Heute
> Assignee: Khoi Nguyen
> Labels: done, portal-s53
> Fix For: 3.2.0-GA
>
> Original Estimate: 1 day
> Time Spent: 6 hours
> Remaining Estimate: 2 hours
>
> I've tried to use a context-root with a slash "/" in a JSR-286 Hello World Portlet and it throws the following exception when trying to add it to a new page:
> 11:59:46,926 ERROR [STDERR] org.gatein.pc.api.NoSuchPortletException: No such portlet /oag.ade
> 11:59:46,926 ERROR [STDERR] at org.gatein.pc.portlet.container.ContainerPortletInvoker.getPortlet(ContainerPortletInvoker.java:99)
> Changing context-root to not contain slashes has fixed the problem.
> Problem happens when using slashes "/" in:
> application.xml of an .ear file
> <module>
> <web>
> <web-uri>seamBookingPortlet.war</web-uri>
> <context-root>/oag/ade</context-root>
> </web>
> </module>
> Changing it to <context-root>/oag-ade</context-root> fixes the problem
> jboss-web.xml of a .war file
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-web>
> <context-root>/LG_1648_1_WEB/SamplePortlet</context-root>
> </jboss-web>
> Changing it to <context-root>/LG_1648_1_WEB.SamplePortlet</context-root> fixes the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (GTNPORTAL-1869) Chrome - processAction methods are called twice when url is empty in logo portlet
by Michal Vanco (JIRA)
Chrome - processAction methods are called twice when url is empty in logo portlet
---------------------------------------------------------------------------------
Key: GTNPORTAL-1869
URL: https://issues.jboss.org/browse/GTNPORTAL-1869
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: User Interface
Affects Versions: 3.1.0-GA
Environment: EPP5.1.0 GA, GateIn trunk (2011/04/12)
Chrome browser
Reporter: Michal Vanco
Fix For: 3.2.0-GA
This is a very interesting behavior which is happening in Chrome (works fine in FF).
To simulate the issue, put logo portlet on page (with empty URL) and add any simple portlet which calls some processAction method (for example some simple form submit).
What is happening is that action is called properly (for example some value is submitted) and when the page is rendered, same processAction is mysteriously called once more (and null values are sent in params).
Thanks Viliam for help with finding this issue!
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Assigned: (GTNPORTAL-1855) The GenericFilter should be called after that the request context has been properly set (ecmdemo portal, sample portal)
by Minh Hoang TO (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-1855?page=com.atlassian.jira.pl... ]
Minh Hoang TO reassigned GTNPORTAL-1855:
----------------------------------------
Assignee: Minh Hoang TO
> The GenericFilter should be called after that the request context has been properly set (ecmdemo portal, sample portal)
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-1855
> URL: https://issues.jboss.org/browse/GTNPORTAL-1855
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Common integration
> Reporter: Martin Weiler
> Assignee: Minh Hoang TO
> Labels: backlogs, done, portal-s52
> Fix For: 3.2.0-GA
>
>
> The changes applied to 02portal.war/WEB-INF/web.xml as a result of the fix for JBEPP-486 also need to be applied to the web.xml files contained in the eppsp demo portal and sample portal. The filter mapping element for the GenericFilter has to be the last one in the list:
> <!-- other filter-mapping declarations -->
> <filter-mapping>
> <filter-name>GenericFilter</filter-name>
> <url-pattern>/*</url-pattern>
> </filter-mapping>
> <!-- ================================================================== -->
> <!-- LISTENER -->
> <!-- ================================================================== -->
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Resolved: (GTNPORTAL-1855) The GenericFilter should be called after that the request context has been properly set (ecmdemo portal, sample portal)
by Minh Hoang TO (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-1855?page=com.atlassian.jira.pl... ]
Minh Hoang TO resolved GTNPORTAL-1855.
--------------------------------------
Resolution: Done
> The GenericFilter should be called after that the request context has been properly set (ecmdemo portal, sample portal)
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-1855
> URL: https://issues.jboss.org/browse/GTNPORTAL-1855
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Common integration
> Reporter: Martin Weiler
> Assignee: Minh Hoang TO
> Labels: backlogs, done, portal-s52
> Fix For: 3.2.0-GA
>
>
> The changes applied to 02portal.war/WEB-INF/web.xml as a result of the fix for JBEPP-486 also need to be applied to the web.xml files contained in the eppsp demo portal and sample portal. The filter mapping element for the GenericFilter has to be the last one in the list:
> <!-- other filter-mapping declarations -->
> <filter-mapping>
> <filter-name>GenericFilter</filter-name>
> <url-pattern>/*</url-pattern>
> </filter-mapping>
> <!-- ================================================================== -->
> <!-- LISTENER -->
> <!-- ================================================================== -->
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months