April 2011 - gatein-issues - Jboss List Archives

[JBoss JIRA] Created: (GTNPORTAL-1863) A constructor with isAutoUpload parameter for UIFormUploadInput

by Vu Viet Phuong (JIRA)

A constructor with isAutoUpload parameter for UIFormUploadInput --------------------------------------------------------------- Key: GTNPORTAL-1863 URL: https://issues.jboss.org/browse/GTNPORTAL-1863 Project: GateIn Portal Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 3.1.0-GA Reporter: Vu Viet Phuong Assignee: Vu Viet Phuong Fix For: 3.2.0-GA UIFormUploadInput have isAutoUpload attribute , but it don't have any constructor it initialize that attribute --> it's hard to use it with UIFormMultivalueInputSet -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1613) Deleting current portal caused redirect to default portal in public mode

by Michal Vanco (JIRA)

Deleting current portal caused redirect to default portal in public mode ------------------------------------------------------------------------ Key: GTNPORTAL-1613 URL: https://jira.jboss.org/browse/GTNPORTAL-1613 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.1.0-GA Environment: EPP5.1.0 ER03 Reporter: Michal Vanco See description at JBEPP-599 -- 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

14 years, 11 months

6
15
0 / 0

[JBoss JIRA] Created: (GTNWSRP-205) Nodetype not found wsrp:portletcontext when import portlet

by Michal Vanco (JIRA)

Nodetype not found wsrp:portletcontext when import portlet ---------------------------------------------------------- Key: GTNWSRP-205 URL: https://issues.jboss.org/browse/GTNWSRP-205 Project: GateIn WSRP Issue Type: Bug Environment: GateIn wsrp-extraction branch, wsrp 2.1.0-Alpha01-SNAPSHOT Reporter: Michal Vanco Assignee: Chris Laprun Fix For: 2.0.1-GA Attachments: wsrp-import.txt There is an issue in wsrp-extraction branch when importing portlet. Exact steps to reproduce: (have 1 remotable portlet deployed - any) - sign in, go to wsrp page - export some portlet - import exported portlet (select portlet, page, window), click on Import button will reproduce the error (attached): javax.jcr.nodetype.NoSuchNodeTypeException: Nodetype not found wsrp:portletcontext Actually the portlet is imported, but it cause other serious problem - consumer can't be deleted: javax.xml.ws.soap.SOAPFaultException: Cannot remove removed node -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-1868) NPE on PortalRequestContext.getTitle

by Chris Laprun (JIRA)

NPE on PortalRequestContext.getTitle ------------------------------------ Key: GTNPORTAL-1868 URL: https://issues.jboss.org/browse/GTNPORTAL-1868 Project: GateIn Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Chris Laprun How to reproduce: 0. Deploy a remotable portlet in GateIn 1. Go to http://localhost:8080/portal/login?initialURI=%2Fportal%2Fprivate%2Fclass... 2. Refresh selfv2 consumer 3. Click on export portlets 4. Select the remote portlet to export 5. Click on export 6. Click on use for import 7. Check the checkbox besides the exported portlet name 8. Select Home page in the page list 9. Click on import 10. BOOM! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

1
4
0 / 0

[JBoss JIRA] Created: (GTNMAVEN-25) Add google javascript clojure compiler to gatein-dep

by Julien Viet (JIRA)

Add google javascript clojure compiler to gatein-dep ---------------------------------------------------- Key: GTNMAVEN-25 URL: https://issues.jboss.org/browse/GTNMAVEN-25 Project: GateIn Maven Issue Type: Task Reporter: Julien Viet Fix For: dep-1.1.0-Beta03 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

1
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-198) Use the Closure compiler in the Javascript serving engine

by Julien Viet (JIRA)

Use the Closure compiler in the Javascript serving engine --------------------------------------------------------- Key: GTNPORTAL-198 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-198 Project: GateIn Portal Issue Type: Feature Request Reporter: Julien Viet http://code.google.com/closure/compiler/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

7
15
0 / 0

[JBoss JIRA] Updated: (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 updated GTNPORTAL-1855: ------------------------------------- Labels: backlogs done portal-s52 (was: backlogs portal-s52 worked) > 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 > 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: >  > <filter-mapping> > <filter-name>GenericFilter</filter-name> > <url-pattern>/*</url-pattern> > </filter-mapping> >  >  >  -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

1
0
0 / 0

[JBoss JIRA] Updated: (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 updated GTNPORTAL-1855: ------------------------------------- Labels: backlogs portal-s52 worked (was: backlogs portal-s52) > 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 > Labels: backlogs, portal-s52, worked > 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: >  > <filter-mapping> > <filter-name>GenericFilter</filter-name> > <url-pattern>/*</url-pattern> > </filter-mapping> >  >  >  -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

1
0
0 / 0

[JBoss JIRA] Commented: (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 commented on GTNPORTAL-1855: ------------------------------------------ There is also sample portal in GateIn > 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 > Labels: backlogs, portal-s52, worked > 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: >  > <filter-mapping> > <filter-name>GenericFilter</filter-name> > <url-pattern>/*</url-pattern> > </filter-mapping> >  >  >  -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

1
0
0 / 0

[JBoss JIRA] Created: (GTNWSRP-123) Seam portlet using portal authentication doesn't work over WSRP2

by Michal Vanco (JIRA)

Seam portlet using portal authentication doesn't work over WSRP2 ---------------------------------------------------------------- Key: GTNWSRP-123 URL: https://jira.jboss.org/browse/GTNWSRP-123 Project: GateIn WSRP Issue Type: Bug Affects Versions: 2.0.0-Beta05 Environment: EPP5.1.0 ER03 seam booking demo (bundled in EPP: jboss-epp-5.1/portletbridge/examples/seamEAR.ear) Reporter: Michal Vanco Assignee: Chris Laprun Fix For: 2.0.0-CR01 It seems like portlet over WSRP is not able to deal with portal authentication. For example seam booking demo works only if you are logged in. But this porltet over WSRP doesn't work and behaves like I'm not logged in all the time. Result is that I'm not able to use this portlet at all because hotel searching isn't available. -- 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

14 years, 12 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 April 2011