October 2012 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPC-86) Add support for CDI portlets

by Ken Finnigan (JIRA)

Ken Finnigan created GTNPC-86: --------------------------------- Summary: Add support for CDI portlets Key: GTNPC-86 URL: https://issues.jboss.org/browse/GTNPC-86 Project: GateIn Portlet Container Issue Type: Feature Request Reporter: Ken Finnigan Fix For: 2.3.3-GA -- 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, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (GTNPC-40) Implement cache scope

by Julien Viet (JIRA)

Implement cache scope --------------------- Key: GTNPC-40 URL: https://jira.jboss.org/browse/GTNPC-40 Project: GateIn Portlet Container Issue Type: Task Reporter: Julien Viet Assignee: Julien Viet Fix For: 2.3.0-GA This will be useful for more efficient caching. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
6
0 / 0

[JBoss JIRA] (GTNPC-85) Cannot build from scratch without privileged access to JBoss legacy repository

by Chris Laprun (JIRA)

Chris Laprun created GTNPC-85: --------------------------------- Summary: Cannot build from scratch without privileged access to JBoss legacy repository Key: GTNPC-85 URL: https://issues.jboss.org/browse/GTNPC-85 Project: GateIn Portlet Container Issue Type: Bug Affects Versions: 2.3.2-GA Reporter: Chris Laprun Fix For: 2.3.3-GA If you try to build PC with a clean environment without priviledged access to JBoss' legacy repo, you will get the following (or similar) error: [ERROR] Failed to execute goal on project pc-test-core: Could not resolve dependencies for project org.gatein.pc:pc-test-core:jar:2.3.3-GA-SNAPSHOT: Failed to collect dependencies for [org.gatein.common:common-logging:jar:2.0.4-GA (compile), org.gatein.wci:wci-wci:jar:2.2.0-Beta01 (compile), org.gatein.pc:pc-controller:jar:2.3.3-GA-SNAPSHOT (compile), org.gatein.pc:pc-portlet:jar:2.3.3-GA-SNAPSHOT (compile), org.gatein.pc:pc-api:jar:2.3.3-GA-SNAPSHOT (compile), log4j:log4j:jar:1.2.16 (compile), org.jboss.unit:jboss-unit:jar:1.2.4 (compile), org.jboss.unit:jboss-unit-remote:jar:1.2.4 (compile), org.jboss.unit:jboss-unit-tooling-ant:jar:1.2.4 (compile), org.jboss.unit:portal-test:jar:1.2.4 (compile), org.jboss.unit:portal-test-generic:jar:1.2.4 (compile), org.jboss.remoting:jboss-remoting:jar:2.5.0.GA (compile), concurrent:concurrent:jar:1.3.4 (test), jboss:jboss-serialization:jar:1.0.3.GA (test), org.jboss.logging:jboss-logging-jdk:jar:2.0.5.GA (compile), org.jboss.logging:jboss-logging-log4j:jar:2.0.5.GA (compile), commons-logging:commons-logging:jar:1.1.1 (compile), commons-httpclient:commons-httpclient:jar:3.1 (compile), javax.ccpp:ccpp:jar:1.0 (compile), javax.portlet:portlet-api:jar:2.0 (compile), org.apache.maven:maven-ant-tasks:jar:2.1.1 (compile), org.slf4j:slf4j-simple:jar:1.5.8 (test)]: Failed to read artifact descriptor for apache-log4j:log4j:jar:1.2.14: Could not transfer artifact apache-log4j:log4j:pom:1.2.14 from/to repository.jboss.org (http://repository.jboss.org/maven2/): Access denied to: http://repository.jboss.org/maven2/apache-log4j/log4j/1.2.14/log4j-1.2.14... -> [Help 1] Repository needs to be explicitly set in the POM file (so that folks trying to build don't have to set it) and exclusions should be added to dependencies to avoid pulling useless dependencies. -- 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, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (GTNPC-64) Update maven profiles.

by Chris Laprun (JIRA)

Update maven profiles. ---------------------- Key: GTNPC-64 URL: https://issues.jboss.org/browse/GTNPC-64 Project: GateIn Portlet Container Issue Type: Feature Request Affects Versions: 2.3.0-Beta03 Reporter: Chris Laprun Fix For: 2.3.0-Beta04 Profiles seem to be outdated. They should be updated to reflect proper module information. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (GTNPC-71) FederatingPortletInvoker cannot properly be used in a distributed context

by Chris Laprun (JIRA)

FederatingPortletInvoker cannot properly be used in a distributed context ------------------------------------------------------------------------- Key: GTNPC-71 URL: https://issues.jboss.org/browse/GTNPC-71 Project: GateIn Portlet Container Issue Type: Bug Affects Versions: 2.3.0-Beta05 Reporter: Chris Laprun Assignee: Chris Laprun 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, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (GTNPC-63) Determine which modules need to be exported as maven artifacts and update the release profile consequently.

by Chris Laprun (JIRA)

Determine which modules need to be exported as maven artifacts and update the release profile consequently. ----------------------------------------------------------------------------------------------------------- Key: GTNPC-63 URL: https://issues.jboss.org/browse/GTNPC-63 Project: GateIn Portlet Container Issue Type: Feature Request Affects Versions: 2.3.0-Beta03 Reporter: Chris Laprun Fix For: 2.3.0-Beta04 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
5
0 / 0

[JBoss JIRA] (GTNPORTAL-2668) There is portlet named "Gadget Wrapper Portlet" in the list of availabel portlets

by Vlastislav Ramik (JIRA)

Vlastislav Ramik created GTNPORTAL-2668: ------------------------------------------- Summary: There is portlet named "Gadget Wrapper Portlet" in the list of availabel portlets Key: GTNPORTAL-2668 URL: https://issues.jboss.org/browse/GTNPORTAL-2668 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.4.0.Final Environment: JBoss AS 7.1.3 Reporter: Vlastislav Ramik Fix For: 3.5.0.Beta01 When you adding portlet into category in application registry, there is "Gadget Wrapper Portlet" listed in available portlets. The portlet is actually Gadget Calendar. If the calendar should be there rename it to calendar. In that case why aren't here other gadgets. If the calendar shouldn't be there remove it form there. -- 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

13 years, 2 months

4
8
0 / 0

[JBoss JIRA] (GTNPORTAL-2674) Clustering isolation is broken on AS7 - usage of JBoss Cache implementation for JCR/kernel

by Michal Vanco (JIRA)

Michal Vanco created GTNPORTAL-2674: --------------------------------------- Summary: Clustering isolation is broken on AS7 - usage of JBoss Cache implementation for JCR/kernel Key: GTNPORTAL-2674 URL: https://issues.jboss.org/browse/GTNPORTAL-2674 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Performance, Security Affects Versions: 3.4.0.Final Environment: GateIn master (3.5.0-SNAPSHOT) from 15 Oct Reporter: Michal Vanco Fix For: 3.5.0.Beta01 Attachments: probe1.txt, probe2.txt I'm hitting an issue with clustering isolation. To reproduce: - use two machines - start first node with: sh standalone.sh -u 239.1.2.3 -c standalone-ha.xml -b ... - start second node with: sh standalone.sh -u 239.3.2.1 -c standalone-ha.xml -b ... (keep in mind that these nodes/ do not share gatein data dir, neither datasources - I don't want to have them connected, I just want to have them started in cluster profile) You will see in log: 12:14:56,760 INFO [org.jboss.cache.RPCManagerImpl] (Incoming-1,null) Received new cluster view: [perf12-5427|1] [perf12-5427, perf13-30570] 12:14:57,171 INFO [org.jboss.cache.RPCManagerImpl] (Incoming-2,null) Received new cluster view: [perf12-65192|1] [perf12-65192, perf13-9838] 12:14:59,996 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,null) ISPN000094: Received new cluster view: [perf12-5984|1] [perf12-5984, perf13-24868] 12:15:00,614 INFO [org.jboss.cache.RPCManagerImpl] (Incoming-1,null) Received new cluster view: [perf12-53815|1] [perf12-53815, perf13-10269] If you really want to join the cluster, you should see something like: 12:26:03,894 INFO [org.jboss.as.clustering] (Incoming-1,null) JBAS010225: New cluster view for partition web (id: 1, delta: 1, merge: false) : [perf13/web, perf12/web] 12:26:03,894 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,null) ISPN000094: Received new cluster view: [perf13/web|1] [perf13/web, perf12/web] -u parameter (jboss.default.multicast.address) should take care of clusters isolation (confirmed by EAP QE). I've also tried to use probe.sh (from epp 5.2) and I'm attaching output - probe1.txt is after start of first node (on perf12) - probe2.txt is after start of second node (on perf13) Clusters are joined during IDM & JCR initialization. There could be some out-of-date implementation of JBoss Cache for cluster implementation of JCR and kernel services :/ -- 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

13 years, 2 months

4
9
0 / 0

[JBoss JIRA] (GTNPORTAL-2693) Users can't login with the sample-portal extension deployed on Tomcat

by Trong Tran (JIRA)

Trong Tran created GTNPORTAL-2693: ------------------------------------- Summary: Users can't login with the sample-portal extension deployed on Tomcat Key: GTNPORTAL-2693 URL: https://issues.jboss.org/browse/GTNPORTAL-2693 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.5.0.Beta01 Reporter: Trong Tran Priority: Minor Fix For: 3.5.0.Beta02 -- 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

13 years, 2 months

2
2
0 / 0

[JBoss JIRA] (GTNPORTAL-2560) Validation of new user - first/last name

by Michal Vanco (JIRA)

Michal Vanco created GTNPORTAL-2560: --------------------------------------- Summary: Validation of new user - first/last name Key: GTNPORTAL-2560 URL: https://issues.jboss.org/browse/GTNPORTAL-2560 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Environment: GateIn master - 3.4.0/ AS7.1.2 Reporter: Michal Vanco Fix For: 3.5.0.Final There is a change at validation of users's first/last name. It says: "Only letters or spaces are allowed for the field "First Name"", but there is a problem with names including "-", "'" etc. (Jean-Claude) This shouldn't be too strict. -- 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

13 years, 2 months

3
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues October 2012