November 2011 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-2282) Remote gadgets can have more than max chars in description

by Matt Wringe (Created) (JIRA)

Remote gadgets can have more than max chars in description ---------------------------------------------------------- Key: GTNPORTAL-2282 URL: https://issues.jboss.org/browse/GTNPORTAL-2282 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Matt Wringe If you import a remote gadget, that gadget's description can be longer than the maximum. But you will not be able to edit a gadget wrapper portlet which contains this gadget since an error message will appear on save: "The length of the text in field "Description :" must be between "0" and "255" characters." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
6
0 / 0

[JBoss JIRA] Created: (GTNWSRP-187) Improve RichFaces support

by Chris Laprun (JIRA)

Improve RichFaces support ------------------------- Key: GTNWSRP-187 URL: https://jira.jboss.org/browse/GTNWSRP-187 Project: GateIn WSRP Issue Type: Feature Request Components: GateIn integration Affects Versions: 2.0.0-CR03 Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.1.0 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (GTNWSRP-184) Richfaces - editor

by Michal Vanco (JIRA)

Richfaces - editor ------------------ Key: GTNWSRP-184 URL: https://jira.jboss.org/browse/GTNWSRP-184 Project: GateIn WSRP Issue Type: Bug Affects Versions: 2.0.0-CR03 Environment: richfacesPortlet from 2.1.0.CR2.EPP51 Reporter: Michal Vanco Assignee: Chris Laprun Editor is not visible at all. (only right pane) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
11
0 / 0

[JBoss JIRA] (GTNPORTAL-2267) Document WS-Security support in WSRP

by Chris Laprun (Created) (JIRA)

Document WS-Security support in WSRP ------------------------------------ Key: GTNPORTAL-2267 URL: https://issues.jboss.org/browse/GTNPORTAL-2267 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, WSRP integration Affects Versions: 3.2.0-M01 Reporter: Chris Laprun Assignee: Matt Wringe Fix For: 3.2.0-Beta01 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
6
0 / 0

[JBoss JIRA] (GTNPC-78) Text encoding is lost in serveResources

by Martin Weiler (Created) (JIRA)

Text encoding is lost in serveResources ---------------------------------------- Key: GTNPC-78 URL: https://issues.jboss.org/browse/GTNPC-78 Project: GateIn Portlet Container Issue Type: Bug Components: API Affects Versions: 2.2.0-GA Reporter: Martin Weiler When a resource is served the content type (mime type) is checked. If the mime type starts with "text" (org.exoplatform.portal.webui.application.UIPortletActionListener line 440-444) a new String is created (org.gatein.pc.api.invocation.response.ContentResponse line 127) If a file was uploaded with a different encoding than the current file encoding this makes the String unreadable. ContentResponse.getContent() creates a new String using the String(byte[]) constructor. In this case the file encoding used on the server is used. This might be a different encoding (e.g. UTF-8) causing the text to be scrambled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
4
0 / 0

[JBoss JIRA] (GTNPORTAL-2278) Enable customization of LocalConfig service by extending existing implementations

by Martin Weiler (Created) (JIRA)

Enable customization of LocalConfig service by extending existing implementations --------------------------------------------------------------------------------- Key: GTNPORTAL-2278 URL: https://issues.jboss.org/browse/GTNPORTAL-2278 Project: GateIn Portal Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Internationalization and Localization, Java API Affects Versions: 3.2.0-M01 Reporter: Martin Weiler Creating custom implementations of the LocaleConfig and LocaleConfigService interfaces is not possible by extending the existing implementations. Most methods are declared final or private. The current implementations should be changed so that they can be easily extended. Otherwise unnecessary code duplication has to be done. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
3
0 / 0

[JBoss JIRA] (GTNPC-76) Hotdeploy of a portlet war, see the portlet.xml loaded before the web.xml

by Dimitri BAELI (Created) (JIRA)

Hotdeploy of a portlet war, see the portlet.xml loaded before the web.xml ------------------------------------------------------------------------- Key: GTNPC-76 URL: https://issues.jboss.org/browse/GTNPC-76 Project: GateIn Portlet Container Issue Type: Quality Risk Reporter: Dimitri BAELI CONTEXT: * A war with a portlet deployed in EPP/GateIn PROBLEM: * As seen in the Forum (http://community.jboss.org/thread/157804) the servlet / portlet init order is changing between normal startup and hotdeploy. * This breaks the hotdeployment of Spring MVC Portlets (which requires the Spring RootContext to be initialized). * This is a quality risk as the loading order is not consitent * This breaks the hotdeployment feature of JBossStudio of manual HotDeployment, and it's a huge pain for developpers REPRODUCE: * To reproduce, I've created a minimalist project (without Spring) that shows the difference between start order init order (normal/hotdeploy). * Put the war in a EPP/GateIn deploy dir * Start the server * The logs will contain this for the fresh start-up: {code} 03:14:47,514 INFO [STDOUT] SampleServlet init. ... 03:15:38,088 INFO [STDOUT] HelloWorldPortlet init. {code} * Touch the war file in the deploy dir * The logs will contain this for the fresh start-up: {code} 03:16:24,907 INFO [TomcatDeployment] undeploy, ctxPath=/PortletAndServletLoadOrderTest 03:16:24,979 INFO [STDOUT] HelloWorldPortlet destroy. 03:16:25,180 WARN [MainResourceResolver] Cannot find servlet context module 03:16:25,181 INFO [STDOUT] SampleServlet destroy. 03:16:25,322 INFO [TomcatDeployment] deploy, ctxPath=/PortletAndServletLoadOrderTest 03:16:25,461 INFO [STDOUT] HelloWorldPortlet init. 03:16:25,467 INFO [STDOUT] SampleServlet init. {code} * Where we see that the Portlet is inited before the portlet EXPECTED: * web.xml is initialized before portlet.xml when the war is Hotdeployed, like during a normal startup -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

6
12
0 / 0

[JBoss JIRA] Created: (GTNPC-74) Add some random value to the common.xml artifact

by Julien Viet (JIRA)

Add some random value to the common.xml artifact ------------------------------------------------ Key: GTNPC-74 URL: https://issues.jboss.org/browse/GTNPC-74 Project: GateIn Portlet Container Issue Type: Task Reporter: Julien Viet Assignee: Julien Viet Fix For: 2.3.0-GA -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1730) samples portlet.xml : cannot validate against portlet-app_2_0.xsd - element init-param at wrong place.

by Antoine Herzog (JIRA)

samples portlet.xml : cannot validate against portlet-app_2_0.xsd - element init-param at wrong place. ------------------------------------------------------------------------------------------------------ Key: GTNPORTAL-1730 URL: https://issues.jboss.org/browse/GTNPORTAL-1730 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation, QA Affects Versions: 3.1.0-GA Reporter: Antoine Herzog Assignee: Luc Texier Priority: Trivial In many of the samples, such as jsfhellouser, the portlet.xml, that have the <init-param> element, cannot validate against the schema : http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd. In eclipse, you can see it directly with a validation error. The error message is : cvc-complex-type.2.4.a: Invalid content was found starting with element 'init-param'. One of '{"http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":portlet-preferences, "http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":security-role-ref, "http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":supported-processing-event, "http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":supported-publishing-event, "http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":supported-public-render-parameter, "http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd":container-runtime-option}' is expected. The turnaround is simple : move the <init-param> element(s) after the <portlet-class> element, and before the <supports> element. Simple, but it would be more clean if the file directly with that. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1718) Move LocalePolicy configuration outside of JAR file

by Marek Posolda (JIRA)

Move LocalePolicy configuration outside of JAR file --------------------------------------------------- Key: GTNPORTAL-1718 URL: https://jira.jboss.org/browse/GTNPORTAL-1718 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.1.0-GA Environment: EPP 5.1.0 CR1 and GateIn reference guide (chapter Localization configuration) Reporter: Marek Posolda Fix For: 3.2.0-GA See JBEPP-702 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues November 2011