January 2012 - gatein-issues - Jboss List Archives

[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

13 years, 9 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

13 years, 9 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

13 years, 9 months

3
5
0 / 0

[JBoss JIRA] (GTNPORTAL-2335) System nodes can be deleted

by Nick Scavelli (JIRA)

Nick Scavelli created GTNPORTAL-2335: ---------------------------------------- Summary: System nodes can be deleted Key: GTNPORTAL-2335 URL: https://issues.jboss.org/browse/GTNPORTAL-2335 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.2.0-Beta01 Reporter: Nick Scavelli If a system node is a subnode of a regular node, it can be deleted with its parent in the _Navigation Management_. -- 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

13 years, 9 months

2
2
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

13 years, 9 months

2
5
0 / 0

[JBoss JIRA] (GTNMGMT-37) SCP login fails due to username and password not being available.

by Nick Scavelli (JIRA)

Nick Scavelli created GTNMGMT-37: ------------------------------------ Summary: SCP login fails due to username and password not being available. Key: GTNMGMT-37 URL: https://issues.jboss.org/browse/GTNMGMT-37 Project: GateIn Management Issue Type: Bug Security Level: Public (Everyone can see) Components: cli Affects Versions: 1.0.0-GA Reporter: Nick Scavelli Assignee: Nick Scavelli -- 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

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] (GTNPORTAL-2322) Update JOSSO section in SSO documentation according to GTNSSO-1

by Marek Posolda (Created) (JIRA)

Update JOSSO section in SSO documentation according to GTNSSO-1 --------------------------------------------------------------- Key: GTNPORTAL-2322 URL: https://issues.jboss.org/browse/GTNPORTAL-2322 Project: GateIn Portal Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 3.2.0-Beta01 Reporter: Marek Posolda Assignee: Marek Posolda Fix For: 3.2.0-CR01 Thanks to GTNSSO-1 we supports JOSSO 1.8.1 but also newer versions like 1.8.2 and 1.8.3. But we need to use different packaging for different JOSSO versions and documentation needs to be updated according to new packaging. -- 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

13 years, 9 months

3
2
0 / 0

[JBoss JIRA] (GTNPORTAL-2341) Czech localization labels for navigation nodes are missing

by Honza Fnukal (JIRA)

Honza Fnukal created GTNPORTAL-2341: --------------------------------------- Summary: Czech localization labels for navigation nodes are missing Key: GTNPORTAL-2341 URL: https://issues.jboss.org/browse/GTNPORTAL-2341 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Honza Fnukal Priority: Minor Fix For: 3.2.0-CR01 There is a change in file: 02portal.war/WEB-INF/conf/portal/portal/classic/navigation.xml - there used to be internationalization keys and now there are <label xml:lang=".."> elements for all languages. I think this change is because localization of nodes in UI, but Czech language is missing in config file. -- 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

13 years, 9 months

1
2
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

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] (GTNPORTAL-2339) Outdated location of LocalePolicy configuration in docs

by Marek Posolda (JIRA)

Marek Posolda created GTNPORTAL-2339: ---------------------------------------- Summary: Outdated location of LocalePolicy configuration in docs Key: GTNPORTAL-2339 URL: https://issues.jboss.org/browse/GTNPORTAL-2339 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 3.2.0-Beta01 Reporter: Marek Posolda Assignee: Marek Posolda Fix For: 3.2.0-CR01 LocalePolicy is now configured in gatein.ear/02portal.war/WEB-INF/conf/portal/web-configuration.xml, but docs is saying gatein.ear/lib/exo.portal.webui.portal.jar/conf/configuration.xml which is not correct. Docs needs to be fixed. -- 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

13 years, 9 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues January 2012