February 2013 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-2831) A wrong exclusion of ehcache-core maven dependency in the root POM

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2831?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-2831: ---------------------------------- Priority: Major (was: Minor) > A wrong exclusion of ehcache-core maven dependency in the root POM > ------------------------------------------------------------------ > > Key: GTNPORTAL-2831 > URL: https://issues.jboss.org/browse/GTNPORTAL-2831 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.0.Final > Reporter: Trong Tran > Labels: portal-s70 > > the ehcache-core lib is being used at runtime by gadget server. > BUT today it is excluded from shindig-common dependency management in the root POM which will raises a side effect in dependency inheritance: > {code} > <dependency> > <groupId>org.gatein.shindig</groupId> > <artifactId>shindig-common</artifactId> > <version>${org.shindig.version}</version> > <exclusions> > <exclusion> > <groupId>net.sf.ehcache</groupId> > <artifactId>ehcache-core</artifactId> > </exclusion> > </exclusions> > </dependency> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2832) Moving the Gadget window in the dashboard doesn't work

by Trong Tran (JIRA)

Trong Tran created GTNPORTAL-2832: ------------------------------------- Summary: Moving the Gadget window in the dashboard doesn't work Key: GTNPORTAL-2832 URL: https://issues.jboss.org/browse/GTNPORTAL-2832 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.5.0.Final Reporter: Trong Tran Fix For: 3.6.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2831) A wrong exclusion of ehcache-core maven dependency in the root POM

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2831?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-2831: ---------------------------------- Affects Version/s: 3.5.0.Final > A wrong exclusion of ehcache-core maven dependency in the root POM > ------------------------------------------------------------------ > > Key: GTNPORTAL-2831 > URL: https://issues.jboss.org/browse/GTNPORTAL-2831 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.0.Final > Reporter: Trong Tran > Priority: Minor > Labels: portal-s70 > > the ehcache-core lib is being used at runtime by gadget server. > BUT today it is excluded from shindig-common dependency management in the root POM which will raises a side effect in dependency inheritance: > {code} > <dependency> > <groupId>org.gatein.shindig</groupId> > <artifactId>shindig-common</artifactId> > <version>${org.shindig.version}</version> > <exclusions> > <exclusion> > <groupId>net.sf.ehcache</groupId> > <artifactId>ehcache-core</artifactId> > </exclusion> > </exclusions> > </dependency> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2831) A wrong exclusion of ehcache-core maven dependency in the root POM

by Trong Tran (JIRA)

Trong Tran created GTNPORTAL-2831: ------------------------------------- Summary: A wrong exclusion of ehcache-core maven dependency in the root POM Key: GTNPORTAL-2831 URL: https://issues.jboss.org/browse/GTNPORTAL-2831 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Trong Tran Priority: Minor the ehcache-core lib is being used at runtime by gadget server. BUT today it is excluded from shindig-common dependency management in the root POM which will raises a side effect in dependency inheritance: {code} <dependency> <groupId>org.gatein.shindig</groupId> <artifactId>shindig-common</artifactId> <version>${org.shindig.version}</version> <exclusions> <exclusion> <groupId>net.sf.ehcache</groupId> <artifactId>ehcache-core</artifactId> </exclusion> </exclusions> </dependency> {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNWCM-8) Setup Maven Checkstyle plugin

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNWCM-8?page=com.atlassian.jira.plugin.s... ] Peter Palaga updated GTNWCM-8: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/lucasponce/gatein-wcm/pull/7 > Setup Maven Checkstyle plugin > ----------------------------- > > Key: GTNWCM-8 > URL: https://issues.jboss.org/browse/GTNWCM-8 > Project: GateIn WCM > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-1379) Page's title and portlet's title are not localizable

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-1379?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-1379: ---------------------------------------------------- Adam Kovari <akovari(a)redhat.com> made a comment on [bug 793400|https://bugzilla.redhat.com/show_bug.cgi?id=793400] Hello, in what version is this scheduled to be fixed? In JPP 6 beta it seems to be still reproducable: Step to reproduce : - Edit the pages.xml of the classic portal - Change the page title with #{portal.classic.home} - Start the server with a clean jcr Result: - #{portal.classic.home} is display on page title instead of the "Home" label define in classic.properties ressource bundle. > Page's title and portlet's title are not localizable > ---------------------------------------------------- > > Key: GTNPORTAL-1379 > URL: https://issues.jboss.org/browse/GTNPORTAL-1379 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Internationalization and Localization > Affects Versions: 3.1.0-GA > Reporter: Nic Essling > Assignee: Minh Hoang TO > Labels: sprint_38, worked > Fix For: 3.2.0-M01 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Should be localizable via keys in both pages.xml and admin UI. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-1379) Page's title and portlet's title are not localizable

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-1379?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-1379: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=793400 > Page's title and portlet's title are not localizable > ---------------------------------------------------- > > Key: GTNPORTAL-1379 > URL: https://issues.jboss.org/browse/GTNPORTAL-1379 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Internationalization and Localization > Affects Versions: 3.1.0-GA > Reporter: Nic Essling > Assignee: Minh Hoang TO > Labels: sprint_38, worked > Fix For: 3.2.0-M01 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Should be localizable via keys in both pages.xml and admin UI. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNWCM-8) Setup Maven Checkstyle plugin

by Peter Palaga (JIRA)

Peter Palaga created GTNWCM-8: --------------------------------- Summary: Setup Maven Checkstyle plugin Key: GTNWCM-8 URL: https://issues.jboss.org/browse/GTNWCM-8 Project: GateIn WCM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Peter Palaga -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2820) Unable to clone page (PageService) in a different destination

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2820?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-2820: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=916260 > Unable to clone page (PageService) in a different destination > ------------------------------------------------------------- > > Key: GTNPORTAL-2820 > URL: https://issues.jboss.org/browse/GTNPORTAL-2820 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Java API > Affects Versions: 3.5.0.Final > Environment: Gatein 3.5.2 Final > Reporter: Gregory SEBERT > Assignee: Boleslaw Dawidowicz > Fix For: 3.6.0.Final > > > In the PageManagement service, when I clone a page to a different destination, I received an exception : > "Could not clone page " + dst.name + "to existing page " + dst.site.getType() + " with id " + dst.site.getName()); > I have a look at the implementation, I find a typo mistake on line 273: > org.gatein.mop.api.workspace.Page dstRoot = srcSite.getRootPage(); > It should be : > org.gatein.mop.api.workspace.Page dstRoot = dstSite.getRootPage(); > Best regards, > Grégory -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2767) Error Messages when using forward

by Gregory SEBERT (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2767?page=com.atlassian.jira.pl... ] Gregory SEBERT updated GTNPORTAL-2767: -------------------------------------- Attachment: demoportlet.war Portlet test forward > Error Messages when using forward > --------------------------------- > > Key: GTNPORTAL-2767 > URL: https://issues.jboss.org/browse/GTNPORTAL-2767 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Common integration > Affects Versions: 3.5.0.Beta02 > Environment: Gate In 3.5.0 Beta02 on top of EAP6 > Reporter: Frederic Hornain > Attachments: demoportlet.war, error.log, porlets_src.zip > > > Indeed, the customer portal team has an issue regarding the navigation in portal. > They are currently trying navigation. > They would to go to another page by using a forward: > private void executeNavigation(String nodeURL) { > PortalRequestContext requestContext = null; > ServletRequest request = null; > ServletResponse response = null; > String requestContextPath = null; > String trimmedNodeURL = null; > RequestDispatcher dispatcher = null; > requestContext = Util.getPortalRequestContext(); > request = requestContext.getRequest(); > response = requestContext.getResponse(); > requestContextPath = requestContext.getPortalContextPath(); > // Remove the portal context path from the nodeURL > // e.g. if nodeURL = "/portal/hello", and portal context path = "/portal" then trimmedNodeURL = "/hello" > trimmedNodeURL = nodeURL.substring(requestContextPath != null ? requestContextPath.length() : 0); > dispatcher = request.getRequestDispatcher(trimmedNodeURL); > try { > dispatcher.forward(request, response); > } catch (Exception e) { > // TODO > } > } > It works and they are well redirected to the corresponding page. > However, customer receive an error (see attached log file). > Then would it be possible to fix this issue ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues February 2013